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
In a current Wetator test scenario we are not able to tear down and cannot delete test data after test execution from the tested application. That means after test execution there will be some left overs in the application.
To be able to leave a trace, where these leftovers belong to, we would like to add a comment to the data with a reference to the actual Wetator test.
For this purpose it would be great to have an automatically available parameter ${testcase} which would represent the name of the currently running test case e.g. wetator_testform.wett.
The text was updated successfully, but these errors were encountered:
${wetator.test-case} - the primarily executed file's name (without extension) - so wetator_testform for your example
${wetator.test-file} - the file name of the file the variable access is executed from, so for example wetator_testform.wett (may also be a module's file name)
${wetator.browser} - current browser during test execution in the same format as in the configuration file (e.g. FF52)
% migrated from trac
In a current Wetator test scenario we are not able to tear down and cannot delete test data after test execution from the tested application. That means after test execution there will be some left overs in the application.
To be able to leave a trace, where these leftovers belong to, we would like to add a comment to the data with a reference to the actual Wetator test.
For this purpose it would be great to have an automatically available parameter ${testcase} which would represent the name of the currently running test case e.g. wetator_testform.wett.
The text was updated successfully, but these errors were encountered: