Challenge Overview
Topcoder is in the process of developing a new version of the Connect platform, which connects customers with project managers, copilots and competitors to run projects through the Topcoder Platform.
We are happy to bring challenges to our community to help us build one of the main tools our teams and community members will be using soon!
At this stage, we would like to involve the community to test out the functionality that’s been built so far.
Payment Structure and Scoring
1. The participant with the highest number of valid bugs (reproducible by reviewer by following steps & video/screenshot) logged will be declared the winner and will earn the first place payment.
2. Participant with the second highest number of valid bugs logged in will earn the second place payment - $200.
3. For other participant without a winning placement (1st/2nd) we will pay $5 per valid issue. The total amount paid will not exceed the second place prize money.
Project Overview
The new version of Topcoder Connect aims to provide an easy experience for customers and project/challenge managers through a very clean and modern UI.
The goal of this challenge is to perform a blackbox testing at a high-level scenario. You are provided with access to the application, user accounts and descriptions of the tasks so you can make sure they work as expected and to report any misbehavior findings (functional, visual, and so on).
** Notice we're awarding a second placement of $200 for this challenge and also prizes for other participants who don't make it as 1st/2nd.
Issue Logging
All issues need to be logged directly in our Github repository as issues. Fill the issue template (create new issue and follow the showed pattern), additionally provide console errors (if any). Reviewer may change this based on their judgement.
Test Data Conventions
Because the demo server will be shared by all bug hunters, please prefix all data with your handle/initials to avoid conflicting with others. Do NOT edit/delete data that does NOT belong to you.
Sample: I create a new project. I call it “mahestro New Project Title..” - add a prefix (your tc handle).
Coverage
Project listing - https://connectv2.topcoder-dev.com/projects (also logged in home page)
- Search
- Filters (not available to customer role; see more on roles below)
- Sort
- Pagination
- Note: the Price column is not in scope
New project - accessible from top bar in project listing
- Tabs
- Project picker
- Device picker
- Project info
Project dashboard - e.g., https://connectv2.topcoder-dev.com/projects/162
- Project panel
- Status
- Duration: not in scope
- Links: available to all user roles
- Team management: test adding and removing users, changing the owner of a project, and so on. Please see “user role criteria” section below for management rights.
- Status updates: can be created/posted by Manager and Copilot role and are visible/can be replied to by all roles; note: updates may not show up in real-time and require a refresh
Project details/app specification - e.g., https://connectv2.topcoder-dev.com/projects/162/specification/
- App definition
- Questions
- Feature requirements (opens another picker overlay)
- Notes
- File upload
- Design specifications
- Questions
- Notes
- Development specifications
- Questions
- Notes
- Test both the Project panel (on the left) and the main panel (on the right); they should stay in sync
Messages - e.g., https://connectv2.topcoder-dev.com/projects/162/messages/
- Read/write for all user roles
- Notes:
- Pressing the “Enter” button to post is not working; click “Post” to post
- Messages may not show up in real-time and require a refresh
User Role Criteria
There are four user roles in the environment. Please perform testing using all of them.
Customer owner: a Connect user who first creates a project.
Customer team member: a Connect user who is added to a project after it has been created.
Copilot: a Topcoder copilot.
Manager: a Topcoder team member (e.g., a challenge architect or a support manager); note, if a Manager creates a project, they do not become the project owner. Only a customer can “own” the project.
Team management rights by role:
Status management rights by role:
Note:
- The team owner “cancels” a project by deleting it from the Project panel on the Dashboard; a copilot or manager “cancel” by changing the project status.
- In project listing, customer roles can only see their own projects; managers can see (and join) all projects; copilots should only see projects that are “Reviewed” and don’t have an existing copilot (copilots can join those projects).
Target Browsers
- Chrome 50-53 on Mac & Windows
- Firefox 47, 48 on Mac & Windows
- IE 11
- Safari 9+ on Mac & Windows
Supported screens
- Desktop
- Tablet down to 768px width
- Mobile NOT supported (out of scope)
Test Server/Account Credentials
pat_monahan: manager role
cp-superstar: copilot role
christina_uw: connect user role
password (for all accounts): topcoder123!
Use this URL to log in: https://accounts.topcoder-dev.com/connect, but test at this URL: https://connectv2.topcoder-dev.com
Known Issues
- The repo issues list contains 26 items labeled as “known-issue”. Those issues are not in scope for your test. You will not get credit for issues filed that are the same as a “known-issue.”
- Major known issues include:
-- Autoload/autorefresh of messages and status updates not working.
-- File upload not working occasionally.
-- Copilots may not be seeing the correct set of projects in project listing.
-- Pressing the “Enter” button to post is not working; click “Post” to post.
- You should test only the app itself; related experiences, such as email notifications, are not in scope.
- Additionally, Login/Registration is not in scope. Use this URL to log in: https://accounts.topcoder-dev.com/connect
Bug Hunting Rules
1. Before you log your issue, ensure that there is no similar issue already logged in. You can do a quick keyword search and only when you are sure that there is no other ticket logged for the same issue, create one.
2. Simple issues related to spelling and grammar may not count.
3. Issues must be clearly described. Provide a test case (perhaps an unlisted video reproducing the issue or a document with steps on how to reproduce the issue) along with the expected vs actual results in order for your issue to be counted.
4. Video and/or screenshots in your issue description are MANDATORY. Any issue without a video or screenshot will be considered INVALID.
5. If an issue is not properly documented, we may reject it and it will not count.
6. If you submit an issue that is seen in multiple screens as multiple issues, they will only count as one. Others will be marked as duplicate.
7. The first participant to find an issue gets the credit - duplicate issues will not be counted.
8. Only create issues until the submission phase. After that, any issue logged will not count.
9. We will mark the issue as accepted, rejected or duplicate.
- Indicate your handle and your Github username.
We are happy to bring challenges to our community to help us build one of the main tools our teams and community members will be using soon!
At this stage, we would like to involve the community to test out the functionality that’s been built so far.
Payment Structure and Scoring
1. The participant with the highest number of valid bugs (reproducible by reviewer by following steps & video/screenshot) logged will be declared the winner and will earn the first place payment.
2. Participant with the second highest number of valid bugs logged in will earn the second place payment - $200.
3. For other participant without a winning placement (1st/2nd) we will pay $5 per valid issue. The total amount paid will not exceed the second place prize money.
Project Overview
The new version of Topcoder Connect aims to provide an easy experience for customers and project/challenge managers through a very clean and modern UI.
The goal of this challenge is to perform a blackbox testing at a high-level scenario. You are provided with access to the application, user accounts and descriptions of the tasks so you can make sure they work as expected and to report any misbehavior findings (functional, visual, and so on).
** Notice we're awarding a second placement of $200 for this challenge and also prizes for other participants who don't make it as 1st/2nd.
Issue Logging
All issues need to be logged directly in our Github repository as issues. Fill the issue template (create new issue and follow the showed pattern), additionally provide console errors (if any). Reviewer may change this based on their judgement.
Test Data Conventions
Because the demo server will be shared by all bug hunters, please prefix all data with your handle/initials to avoid conflicting with others. Do NOT edit/delete data that does NOT belong to you.
Sample: I create a new project. I call it “mahestro New Project Title..” - add a prefix (your tc handle).
Coverage
Project listing - https://connectv2.topcoder-dev.com/projects (also logged in home page)
- Search
- Filters (not available to customer role; see more on roles below)
- Sort
- Pagination
- Note: the Price column is not in scope
New project - accessible from top bar in project listing
- Tabs
- Project picker
- Device picker
- Project info
Project dashboard - e.g., https://connectv2.topcoder-dev.com/projects/162
- Project panel
- Status
- Duration: not in scope
- Links: available to all user roles
- Team management: test adding and removing users, changing the owner of a project, and so on. Please see “user role criteria” section below for management rights.
- Status updates: can be created/posted by Manager and Copilot role and are visible/can be replied to by all roles; note: updates may not show up in real-time and require a refresh
Project details/app specification - e.g., https://connectv2.topcoder-dev.com/projects/162/specification/
- App definition
- Questions
- Feature requirements (opens another picker overlay)
- Notes
- File upload
- Design specifications
- Questions
- Notes
- Development specifications
- Questions
- Notes
- Test both the Project panel (on the left) and the main panel (on the right); they should stay in sync
Messages - e.g., https://connectv2.topcoder-dev.com/projects/162/messages/
- Read/write for all user roles
- Notes:
- Pressing the “Enter” button to post is not working; click “Post” to post
- Messages may not show up in real-time and require a refresh
User Role Criteria
There are four user roles in the environment. Please perform testing using all of them.
Customer owner: a Connect user who first creates a project.
Customer team member: a Connect user who is added to a project after it has been created.
Copilot: a Topcoder copilot.
Manager: a Topcoder team member (e.g., a challenge architect or a support manager); note, if a Manager creates a project, they do not become the project owner. Only a customer can “own” the project.
Team management rights by role:
Status management rights by role:
Note:
- The team owner “cancels” a project by deleting it from the Project panel on the Dashboard; a copilot or manager “cancel” by changing the project status.
- In project listing, customer roles can only see their own projects; managers can see (and join) all projects; copilots should only see projects that are “Reviewed” and don’t have an existing copilot (copilots can join those projects).
Target Browsers
- Chrome 50-53 on Mac & Windows
- Firefox 47, 48 on Mac & Windows
- IE 11
- Safari 9+ on Mac & Windows
Supported screens
- Desktop
- Tablet down to 768px width
- Mobile NOT supported (out of scope)
Test Server/Account Credentials
pat_monahan: manager role
cp-superstar: copilot role
christina_uw: connect user role
password (for all accounts): topcoder123!
Use this URL to log in: https://accounts.topcoder-dev.com/connect, but test at this URL: https://connectv2.topcoder-dev.com
Known Issues
- The repo issues list contains 26 items labeled as “known-issue”. Those issues are not in scope for your test. You will not get credit for issues filed that are the same as a “known-issue.”
- Major known issues include:
-- Autoload/autorefresh of messages and status updates not working.
-- File upload not working occasionally.
-- Copilots may not be seeing the correct set of projects in project listing.
-- Pressing the “Enter” button to post is not working; click “Post” to post.
- You should test only the app itself; related experiences, such as email notifications, are not in scope.
- Additionally, Login/Registration is not in scope. Use this URL to log in: https://accounts.topcoder-dev.com/connect
Bug Hunting Rules
1. Before you log your issue, ensure that there is no similar issue already logged in. You can do a quick keyword search and only when you are sure that there is no other ticket logged for the same issue, create one.
2. Simple issues related to spelling and grammar may not count.
3. Issues must be clearly described. Provide a test case (perhaps an unlisted video reproducing the issue or a document with steps on how to reproduce the issue) along with the expected vs actual results in order for your issue to be counted.
4. Video and/or screenshots in your issue description are MANDATORY. Any issue without a video or screenshot will be considered INVALID.
5. If an issue is not properly documented, we may reject it and it will not count.
6. If you submit an issue that is seen in multiple screens as multiple issues, they will only count as one. Others will be marked as duplicate.
7. The first participant to find an issue gets the credit - duplicate issues will not be counted.
8. Only create issues until the submission phase. After that, any issue logged will not count.
9. We will mark the issue as accepted, rejected or duplicate.
Final Submission Guidelines
- Please submit a text file with the list of bugs filed by you with Github URLs.- Indicate your handle and your Github username.