Topcoder QA Framework - Automation Updates

Challenge Objectives

• Implement missing tests from the provided spreadsheet.

• Update the generated report format.

• Add test case IDs.

• Add test case dependencies to E2E test scenarios.

Project Background

In this series of challenges, we’re creating an E2E testing framework that will help us test different applications within the Topcoder platform.

Currently, we target the Connect app.

Technology Stack

• Node.js

• Selenium

• Webdriver.io

• AWS S3

• CircleCI

Code access

Repo: https://github.com/appirio-tech/qa-framework-js

You will find a self-registration link on the challenge forum in case you don’t have access to the repository.

Individual requirements

1. Implement all missing test cases, steps and scenarios from the provided spreadsheet (see forum).

2. Currently, Allure report shows the test results in 2 levels:
   Test Scenario
   -----| Test case
   We need to be able to see the results in 3 levels like the example below:
   Test scenario
   -----| Test case
   ----------| Step
   You may have to update the structure of the tests to achieve this.
   If this is not possible in Allure report, we need to follow the following structure and tag each test case with the ID of the test scenario:
   Test case
   -----| Step
   In this case, you also need to modify the checkDependencies() method, as well as the afterTest & after hooks to properly identify the scenario/case IDs and properly log the results into the automationStatus.json file.

3. Depending on how you complete the above requirement, you need to tag all test scenarios/cases with the IDs from the “Automation Test Case ID” column.
   Currently, this works by adding the “[AUTOMATION_ID]” prefix to the test case description.
   Eg: it('[GUI_TS_001_LogIn_TC_002] Logo should be displayed on upper left corner', () => { /* … */ });

4. Add dependency check (use the global.checkDependencies() method) to the E2E scenarios. See the “Automation Pre-Condition” column of the “End-2-End Test Cases” sheet.

Documentation updates

You need to update the README.md to reflect the changes made from the above requirements.

Important Notes

Note that the tests will run on CircleCI and not locally.

What To Submit

Submit a git patch for the latest commit in the develop branch. Make sure to mention the exact commit you used so the reviewers can apply your patch.

 

Should you have any doubt, feel free to ask in the challenge forum!

Final Submission Guidelines

Please see above