Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Automatic parameter ${testcase} to get name of currently running test script #15

Open
rbri opened this issue Oct 25, 2021 · 3 comments
Open

Comments

@rbri
Copy link
Member

rbri commented Oct 25, 2021

% 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.

@rbri
Copy link
Member Author

rbri commented Oct 25, 2021

We decided to add three variables:

${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) 

@rbri
Copy link
Member Author

rbri commented Oct 25, 2021

In [2601]:

  • more vars (see #119)

@rbri
Copy link
Member Author

rbri commented Oct 25, 2021

there are no minus inside our varnames so far the current impl uses
${wetator.testcase}
${wetator.testfile}
${wetator.browser}

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant