Goal
Understand key messages from the framework.
- Using associates to fix issues
- Steps definitions updates
Troubleshooting
If you have any questions during training or project, just ask stack overflow if you feel like something doesn’t make sense or you feel stuck in a particular area.
Variables – Unkown parameter
The unknown parameter error will show up if for any reason a user used an incorrect variable
Warning – Failed to locate text
The reason you are seeing this message is because the UI layer has introduced these items – i.e. they are not defined in the configuration, so the config tests have no knowledge of their existence.
Tests run in config mode are designed to test the config and do not have the capability to know how the finished UI looks, however, they will have the capability to test the data that is saved etc. They also run an order of magnitude quicker than the same tests run in UI mode. Likewise, when tests are run in UI mode, they can test things like VRT (Visual Regression Testing) which the config mode tests cannot test for. The moral being that the combination of running the tests in config and UI mode gives you the best coverage so keep writing those tests
Warning – Unknown resource path
The reason of this warning is because the path of the fixture is incorrect. Either way the location is incorrect or the fixture error might be related to case sensitive location. For example the following example is showing the warning due to the F in fixture is uppercase rather than lowercase
