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

Add test scenarios to Test_Suites sheet #22

Open
vivek-dhayalan opened this issue Apr 12, 2022 · 0 comments
Open

Add test scenarios to Test_Suites sheet #22

vivek-dhayalan opened this issue Apr 12, 2022 · 0 comments
Labels
documentation Improvements or additions to documentation enhancement New feature or request input_sheet_restructure

Comments

@vivek-dhayalan
Copy link
Contributor

vivek-dhayalan commented Apr 12, 2022

As part of Input sheet restructuring the first task would be is move the mapping between test scenarios & test suites from test scenarios sheet to test suites sheet.

The following would be task associated with the same:

  1. Remove test_suite column from sheet test_scenarios
  2. Add test_scenarios column to test_suites sheet

leave test_apis column in Test_Scenarios sheet as it is at the moment, we can change it after we fix this ticket.

This would also result in the way we access the context variables. For example, currently the variables are accessed by ${test_scenario_name.test_case_name.request/response}. When we re-define that the scenario can be executed multiple times, then the name spacing should also include the test suite name and the context map have to be saved accordingly.
If the test suite name is not mentioned, then by default the current test_suite will be referenced.

@vivek-dhayalan vivek-dhayalan added the documentation Improvements or additions to documentation label Apr 12, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation enhancement New feature or request input_sheet_restructure
Projects
None yet
Development

No branches or pull requests

1 participant