Test Scenario and Test Case Summaries Creation for Topcoder - Series 2

Challenge Objectives

Create Test Scenario Document covering all the functionalities of the Topcoder’s Challenge Details page, Submission page and View Submission page. Include all the functions, use cases and validations for the ‘Test Case Summary’ column. No need to write test steps and expected results.

 Assets:

Test Scenario Document of the previous challenge is attached for reference. Please use the same format. 

Detailed Requirement:

• In-Scope screens: Challenge Details page, Challenge Submission Page and View Submission page

• No need to cover Header and Footer functions

• Use the first sheet in the excel for ‘Challenge Details page - Before Login Functions’ and the second sheet for ‘Challenge Details page - After Login Functions’. And in the After Login Sheet, highlight the scenarios that are specific to After login. This way, the reviewer knows that what has been covered/modified for the After-login-sheet from the Before-login-Sheet.

• Include separate sheets for ‘Challenge Submission Page’ and ‘View Submission page’

• Make sure to write separate scenarios for each of the following sub-tracks: Code, Bug Hunt, Content Creation, Design, Design F2F, F2F, MM, Web Design, Application Front End Design, Idea Generation. This is to make sure that the Challenge Details Screen of most commonly used challenge types are verified.

• Submissions tab of MM Challenge Details page is different. Please check this with extra care. This is very important. Submission tab of other challenges may vary too. Please check them and write. Do not write for one track and copy the same for others.

• Highlight the keywords in each test case

• Include Test cases to verify that the Challenge details page gets loaded at a considerable time. 

• Include Test cases to verify that :

  • Submission Tab of MM match loads the result at a considerable time

  • Final Ranks and Scores (for MM Matches) are not displayed until the review phase is over

  • Final Provisional score of a submitter is same as the recent provisional score obtained by the submitter

  • Submission histories of MM matches

  • Provisional Ranking is based on the Provisional score obtained by the submitter

  • Final Ranks are based on the Final Scores

  • ‘Submission in Queue’ symbol is displayed when submission is in queue

  • Results are displayed when results are available

  • ‘Submission Failed’ symbol is displayed when the submission failed

• Include scenarios to verify the winners tab for all the Challenge types 

• Include scenarios to verify the Challenge details page of all the Challenge types on different phases like Registration, Checkpoint Submission, Checkpoint Review, Submission, Review, Appeal, Appeal Response, Finished

• Also, pay extra attention to the Design Challenge Details page where it has Checkpoint details and View Submission option. Include scenarios/test cases to verify the ‘View Submission’ page too.

• Include Challenge Tech Tag Function

• Do not submit dummy submissions to challenges to test the functions. Please use Topcoder Dev Environment to test the submission functionality.

• Include any other functions I have missed to note above, for the Challenge Details page, Submission page and View Submission Page.

 

1. Use the app, explore and understand the functions. The Test Scenario Document that would be created via this challenge will be used as a BRD for future references. If you have any questions regarding the functions, please post in the forum.

2. Include the following:

• All Functional Test Cases
• Positive test cases
• Negative test cases
• Integration test cases

3. Do Not include the following:

• All Non Functional Scenarios
• UI/Visual/Accessibility scenarios
• Performance test scenarios
• Security test scenarios

DO NOT REVEAL YOUR IDENTITY in the challenge submission in any way (i.e. in test data or in the file name or in the test email or in any form)

Judging Criteria:

Submissions will be reviewed subjectively based on the following criteria:

• Coverage: How completely test cases cover the functionality

• Maintainability: How well written and easy to understand the test cases are

• Content: How accurate the test cases are

• Quality: Overall quality of the submission

Unlike the previous challenges of this series,  this challenge will have Appeal and Appeal Response phases to address submitter’s concerns (if any) with review comments.

Final Submission Guidelines

Final Submission Guidelines

• Your submission file must be in .xlsx format 

• Zip your test scenario document and submit it. 

IMPORTANT: Submit the above details before the Submission Phase ends.