-
Bug
-
Resolution: Fixed
-
Major
-
4.0.1, 4.1.8, 4.2.5, 4.3.2
The Behat step to check for values in tables is broken and does not give proper results. I'm not sure what's the actual problem, but even something like this passes instead of failing:
Then the following should exist in the "doesnotexist" table:
|
| Name |
|
| thisdoesnotexist |
|
And then some tests that should be passing fail instead, so I don't think this step is doing its job and it may be dangerous to use until it's fixed.
Here's a reproduction with some botched scenarios: https://github.com/NoelDeMartin/moodle-local_sandbox/blob/MDL-75081/tests/behat/sandbox.feature
- caused a regression
-
MDL-80907 Checking table values in Behat is still not exactly correct
- Closed
- has a non-specific relationship to
-
MDL-67334 Behat not correctly checking column values with Selenium
- Closed
-
MDL-78965 Behat to verify that a teacher can set a quiz with certainty-based marking (Automate MDLQA-1166)
- Closed
-
MDL-46817 Add a new behat step to ensure table values exist
- Closed
-
MDL-78097 Unify the search and initials filter in the grader report
- Closed
- Testing discovered
-
MDL-80240 Inconsistent searching in grader report when clicking "View all results"
- Closed
-
MDL-80241 Malformed output when grader tries to filter on user description
- Closed
- will help resolve
-
MDL-79098 Fix existing behat scenarios for asserting table content with one single column
- Closed