You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a test writing simplification proposal raised in the description of #1039 that we agreed not to implement in #1042.
If the author of a test plan wants to add one or more assertions to a subset of commands that are assigned to a test, and if the author wants those assertions to be at the end of the sequence of assertions, then support specifying one or more assertions in the assertionExceptions column of *-commands.csv without specifying those assertions as 0 priority assertions in tests.csv. Thus, the list of assertions that are included for a command includes:
All assertions listed in tests.csv in the order listed in tests.csv that have a non-0 priority in both tests.csv and commands.csv.
All the assertions listed for the command in commands.csv in the order listed in commands.csv where:
Are not present in tests.csv
Have a non-0 priority in commands.csv
The text was updated successfully, but these errors were encountered:
Adding context, last time we went over this @mcking65 mentioned he will discuss with Isabel and confirm whether we would implement it. Bocoup's recommendation was not to move forward with it.
This is a test writing simplification proposal raised in the description of #1039 that we agreed not to implement in #1042.
If the author of a test plan wants to add one or more assertions to a subset of commands that are assigned to a test, and if the author wants those assertions to be at the end of the sequence of assertions, then support specifying one or more assertions in the
assertionExceptions
column of*-commands.csv
without specifying those assertions as 0 priority assertions in tests.csv. Thus, the list of assertions that are included for a command includes:The text was updated successfully, but these errors were encountered: