Test Scenario and Test Cases Summary Creation for Topcoder Challenge Listing and Review Opportunities page

Challenge Objectives

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

There is no Appeals / Appeals Response phase for this challenge. The decision of Copilot / PM is final.

 Assets:

Sample Test Scenario Document Format is attached in the forum. Please use only this format. 

Detailed Requirement:

• In Scope screens: Challenge Listing page: https://www.topcoder.com/challenges and Review Opportunity page. (You can go to Review Opportunity Page by clicking the Apply button available in the ‘Open for Review’ screen)

• No need to cover Header and Footer functions

• Include everything that is present in the Challenges tab

• Anything other than Challenge Listing page and Review Opportunity Page are not in scope

• Include integration between 2 screens even if that navigates the user away from the Challenge Listing page or the Review Opportunity page.

Example: Include scenario to check if clicking on a challenge takes the user to challenge details page 

• Use the first sheet in the excel for ‘Challenge Listing page - Before Login Functions’ and the second sheet for ‘Challenge Listing 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.

• Make sure we write separate scenarios for each of the following subtracks: Code, Bug Hunt, F2F, MM, Web Design, Application Front End Design, Idea Generation. Write once and copy for others. This is to make sure that all types of challenges are working (takes the user to respective challenge details page) when user clicks on it.

• Just include SRMs link navigation. Do not include the arena page.

• Include Search text box

• Include Design, Development, Data Science Filters (Cover ALL combination of these filters). When writing the combination, make sure to verify the counts along with the challenge-display.

• Include the Filters available under the Filter button. 

• Make sure to include each of the values available for a filter

• Include the Right panel filters 

• When writing test cases for combination of filters (Filters available under the filters button, Right Panel Filters and then the Tracks filters), it's not a good practice to write all possible combinations of all values, as we have a lot of values available for each of the filters. Choose strategies that will expose maximum number of bugs. Time to use the techniques like Equivalence Partitioning, Boundary Value Analysis, Decision Table and all other techniques that you learnt during ISTQB. Attach a Readme file describing what technique(s) you have used in writing test case summaries for these FILTER COMBINATIONS and explain how it helps in exposing maximum number of bugs. Things to note here is that, The Development, Data Science and Design Track filters used to break when they are used along with other filters like sub-track, keywords or the right-panel filters. So choose test cases wisely and make sure it helps to discover maximum number of bugs.

• Include Sort functions

• Include scenarios/test cases to verify the count (This is Very Important)

• When verifying the filter and filter-combinations, include the ‘Review Type’ filter available in the ‘Open for Review’ bucket

• Do not test the ‘’Apply for review’ function in the real challenges as it affects the challenge. I will create a dummy challenge for testing this and share in the forum.

• Include ‘View more challenges’ link

• Include ‘My challenges’ present in the Right panel when the user is logged in.

• Include the Challenge Technology Tag functions (These tags are present under each of the challenges)

• Include scenarios to verify the Total Number of Registrants and Submissions for different types of challenges

• Include Test cases to verify that Challenge listing page is loaded at a considerable time 

• Include any other functions I have missed to note above, for the Challenge Listing page and Review Opportunities 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:

   1. All Functional Test Cases

   2. Positive test cases

   3. Negative test cases

   4. Integration test cases

3. Do Not include the following:

   1. All Non Functional Scenarios

   2. UI/Visual/Accessibility scenarios

   3. Performance test scenarios

   4. 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). Anyone doing so, will not be qualified for any prizes. This is to get unbiased reviews from the reviewers.

Judging Criteria:

Following things will be considered during the review:

• Following the instructions given here in the Challenge Specification

• Quality and quantity of the test scenarios and test cases covered

• Look and format (Expecting it to be simple and easy to understand)

Final Submission Guidelines

Final Submission Guidelines

• Your submission file must be in .xlsx format 

• Zip your Test Scenario Document and Readme file and submit it. 

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