Webpage test feedback
When a webpage test cannot find its target it does 1 of 2 things:
- The test will time out with a “Could not Check Task” message, resulting in the automated failure of all subsequent tasks, or
The concerns are that the 1st issue appears to be a technical glitch with the platform to some users (which is not the case) and the 2nd issue doesnt attribute the task failure to the student’s code definitively. “Image not found” is kinda opened ended.
I think two things could be done to improve this:
- On a timeout and precondition failure, fail the task and explicitly declare that the target element was not found in code.
- Remove the “null%difference”
(also open to other suggestions)