Challenge Overview
Challenge Objectives
Create Test Scenario Document covering all the functionalities of the Topcoder’s Accounts app. Include all combination of functions/ use cases / validations / for the ‘Test Case Summary’ column. No need to write test steps and actual results. There is no Appeals / Appeals Response phase for this challenge. Decision of Copilot / PM is final.
Assets:
Sample Test Scenario Format is attached in the forum. Please use only this format.
Detailed Requirement:
- Modules in Scope:
Registration page: https://accounts.topcoder.com/member/registration
Login page: https://accounts.topcoder.com/member
Create New Password page
Forgot password page
Anything in the Accounts app developed by Topcoder are in scope. Include End-to-End scenarios. Example, if the password is sent to email, include test scenario to test the link present in the reset-password mail.
- No need to write extensive test scenarios for apps developed by third parties. Example, Do not write test scenarios to test all features of userway icon (Human icon that is present at the bottom right of the Registration screen). Its enough if we cover one of the functions of userway to make sure the integration works. Choose one that is best suited for automation.
- Use the app, explore and find out all possible scenarios. The Test Scenario Document which would be created via this challenge will be used as a BRD for future references. So cover all possible Test Cases (Test case summary only). Ask any questions you may have in the forum.
- For the ‘Test Case Summary’ column - Make sure we write the ‘action’ as well as ‘expected outcome’.
Examples:
Example: 1 ‘To verify that user is able to login with valid username and password'
Here action is: Login with valid username and password
Expected Outcome is: User is able to login
Example:2 ‘To verify that user can login using valid Github credentials’
Here action is: Login using valid Github credentials
Expected Outcome is: User can login
- Include the following:
All Functional Test Cases
Positive test cases
Negative test cases
Integration test cases (Ex: If you click login with valid credentials, it should land on My-dashboard screen. Though My-Dashboard screen is not part of this challenge, We need to make sure user lands on that page when logging in with correct password)
- Do Not include the following:
All Non Functional Scenarios
UI/Visual/Accessibility scenarios
Performance test scenarios
Security test scenarios
Judging Criteria:
Following things will be considered during the review:
Create Test Scenario Document covering all the functionalities of the Topcoder’s Accounts app. Include all combination of functions/ use cases / validations / for the ‘Test Case Summary’ column. No need to write test steps and actual results. There is no Appeals / Appeals Response phase for this challenge. Decision of Copilot / PM is final.
Assets:
Sample Test Scenario Format is attached in the forum. Please use only this format.
- Modules in Scope:
Registration page: https://accounts.topcoder.com/member/registration
Login page: https://accounts.topcoder.com/member
Create New Password page
Forgot password page
Anything in the Accounts app developed by Topcoder are in scope. Include End-to-End scenarios. Example, if the password is sent to email, include test scenario to test the link present in the reset-password mail.
- No need to write extensive test scenarios for apps developed by third parties. Example, Do not write test scenarios to test all features of userway icon (Human icon that is present at the bottom right of the Registration screen). Its enough if we cover one of the functions of userway to make sure the integration works. Choose one that is best suited for automation.
- Use the app, explore and find out all possible scenarios. The Test Scenario Document which would be created via this challenge will be used as a BRD for future references. So cover all possible Test Cases (Test case summary only). Ask any questions you may have in the forum.
- For the ‘Test Case Summary’ column - Make sure we write the ‘action’ as well as ‘expected outcome’.
Examples:
Example: 1 ‘To verify that user is able to login with valid username and password'
Here action is: Login with valid username and password
Expected Outcome is: User is able to login
Example:2 ‘To verify that user can login using valid Github credentials’
Here action is: Login using valid Github credentials
Expected Outcome is: User can login
- Include the following:
All Functional Test Cases
Positive test cases
Negative test cases
Integration test cases (Ex: If you click login with valid credentials, it should land on My-dashboard screen. Though My-Dashboard screen is not part of this challenge, We need to make sure user lands on that page when logging in with correct password)
- Do Not include the following:
All Non Functional Scenarios
UI/Visual/Accessibility scenarios
Performance test scenarios
Security test scenarios
���All the participants are expected to create testing account only when it is necessary (max 3 testing accounts can be created).
DO NOT REVEAL YOUR IDENTITY in the challenge submission in any way (i.e. in test data or in 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
- Maximum number of unique test cases covered in all the areas with high accuracy
- Look and format (Expecting it to be simple, and easy to understand where is what)
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.