Challenge Overview
Please ignore the prize shown in this challenge. This challenge itself was created for outreach purposes only and there will be no actual winner.
For this Bug bash, we will be paying per accepted fix based on the prize amount noted in each issues title.
Basic requirements for this challenge:
- Bug Bash on Frontend and Backend of Hoherberg Ski School web app
Hoherberg Ski School is very excited to see how the application look on real life based on previous winning storyboard. This web application need build using ASP.Net MVC Core with focus on desktop resolution only.
On this Bug Bash challenge you need fix issues related to Backend and Frontend. We will be paying per accepted fix based on the prize amount noted in each issues title.
Good luck and let's discuss any questions you have. See you in the challenge forum!
Technology Stack
Frontend:
- ASP.Net MVC Core
- HTML5
- CSS3
- Javascript
- Jquery
Backend:
- ASP.Net MVC Core Web API
- MySQL
Storyboard Design Flow:
Reservations: https://marvelapp.com/e683i7j
Scheduler: https://marvelapp.com/9dd26a4
Products/Instructors: https://marvelapp.com/4gjed11
Notifications: https://marvelapp.com/9e1f457
Code Access
Ragnar: Check challenge forum to access all source code
- Use frontend repo > dev branch as frontend source code
- Use backend repo > dev branch as backend source code
- Use frontend repo > frontend-fixes branch for prototype reference
- You can use ‘dotnet run’ from command prompt to running both backend and frontend
- on Mac Os, you need update
- Let us know if you face issues when set up the app.
Login Credentials
Admin/adminPass
Supervisor/supervisorPass
Reservationist/reservationistPass
General Requirements:
- In this Bug Bash challenge, we are looking for your help to fix a bunch of bugs in our repo.
- Read about Bug Bash description here: https://help.topcoder.com/hc/en-us/articles/115002087948-What-is-a-Bug-Bash
- The bug list will be updated frequently, we will be adding new bugs and closing bugs that you and other competitors fix. Make sure to keep watching the GitLab list.
- Keep best practice implementation to create Model View Controller solution on ASP Net Core MVC application
- Please, subscribe yourself to get notifications from this 2 repos to participate in this Bug Bash:
-- Frontend repo: https://gitlab.com/alta-ski/frontend
-- Backend repo: https://gitlab.com/alta-ski/backend
- Click here to register to our Topcoder X Registration Link: https://x.topcoder.com/api/v1/gitlab/groups/registration/77e5292a-0b82-4cfd-9790-d8cb79f64782-1540265251908
Bug Bash Rules:
- Each issue has a dollar value. Dollar values are based upon complexity and priority of issue.
- You can assign any unassigned issue to yourself with a "tcx_OpenForPickup" (first come first serve).
- You must update the label to “tcx_Assigned”, and remove the “tcx_OpenForPickup” label.
- You can only self assign one issue at a time. The nature of it being assigned will indicate if it is not available to anyone else.
- You will fix the ticket as a pull request to the master branch
- Once a ticket is fixed, you should label it "tcx_ReadyForReview" where it will then be verified. If something is still broken, the copilot will comment on the ticket.
- After submitting and tagging "tcx_ReadyForReview" you are eligible to accept another. You can do as many tickets as you want, as long as you follow the rules above.
- If the ticket is fixed properly, your pull request will be merged in, and the ticket will be marked "tcx_FixAccepted".
- If the ticket is “tcx_Feedback”, it should be your first priority to fix the issue.
- When the ticket is closed, payment will be recorded, when we issue the payment the tag will be updated to “tcx_Paid”
- If an assigned task is not done in 24 hours, you will be unassigned from the ticket, and it will be opened back up to the community.
- You can ask questions directly on the ticket comments.
- Bug Bashes are different than Bug Hunts - please make sure to check the contest type in the contest name when registering.
IMPORTANT:
- DO NOT make INDENTATION AND SPACE changes. Please focus on completing challenge Tasks. We need to track your changes so focus only code fixes.
- DO NOT DELETE EXISTING FILES/LIBRARY. Confirm with us if needed.
- RE-TEST AND COMPARE ON all required browsers before you submit
SUBMISSION FLOW
- First, make sure your "dev" branch is ALWAYS UPDATED! We will be pushing new code updates in parallel.
- CREATE NEW BRANCH on related repo with the title format "issues/username/XX" where XX is the number on the GitLab Issue.
- DO NOT FORK into your own repo. you MUST create from our repo. We will reject your submission if you submit from your own repo.
- Start working your fixes in that branch, commit and push to your working repo.
- Once you are satisfied with your fixes, you should label it "tcx_ReadyForReview.
- Next you will send MERGE REQUEST to "dev".
- Put Ticket url you were working on in the Merge Request description.
- If something is still broken, the Reviewer will comment on the ticket. We will update the label as " tcx_Feedback" and you can complete the fixes based on the feedback.
Web Browsers Requirements
Your submission must look and work consistently across these following browsers on the latest versions:
- IE11
- Chrome,
- Edge,
- Safari,
- Firefox
For this Bug bash, we will be paying per accepted fix based on the prize amount noted in each issues title.
Basic requirements for this challenge:
- Bug Bash on Frontend and Backend of Hoherberg Ski School web app
Final Submission Guidelines
Challenge OverviewHoherberg Ski School is very excited to see how the application look on real life based on previous winning storyboard. This web application need build using ASP.Net MVC Core with focus on desktop resolution only.
On this Bug Bash challenge you need fix issues related to Backend and Frontend. We will be paying per accepted fix based on the prize amount noted in each issues title.
Good luck and let's discuss any questions you have. See you in the challenge forum!
Technology Stack
Frontend:
- ASP.Net MVC Core
- HTML5
- CSS3
- Javascript
- Jquery
Backend:
- ASP.Net MVC Core Web API
- MySQL
Storyboard Design Flow:
Reservations: https://marvelapp.com/e683i7j
Scheduler: https://marvelapp.com/9dd26a4
Products/Instructors: https://marvelapp.com/4gjed11
Notifications: https://marvelapp.com/9e1f457
Code Access
Ragnar: Check challenge forum to access all source code
- Use frontend repo > dev branch as frontend source code
- Use backend repo > dev branch as backend source code
- Use frontend repo > frontend-fixes branch for prototype reference
- You can use ‘dotnet run’ from command prompt to running both backend and frontend
- on Mac Os, you need update
- Let us know if you face issues when set up the app.
Login Credentials
Admin/adminPass
Supervisor/supervisorPass
Reservationist/reservationistPass
General Requirements:
- In this Bug Bash challenge, we are looking for your help to fix a bunch of bugs in our repo.
- Read about Bug Bash description here: https://help.topcoder.com/hc/en-us/articles/115002087948-What-is-a-Bug-Bash
- The bug list will be updated frequently, we will be adding new bugs and closing bugs that you and other competitors fix. Make sure to keep watching the GitLab list.
- Keep best practice implementation to create Model View Controller solution on ASP Net Core MVC application
- Please, subscribe yourself to get notifications from this 2 repos to participate in this Bug Bash:
-- Frontend repo: https://gitlab.com/alta-ski/frontend
-- Backend repo: https://gitlab.com/alta-ski/backend
- Click here to register to our Topcoder X Registration Link: https://x.topcoder.com/api/v1/gitlab/groups/registration/77e5292a-0b82-4cfd-9790-d8cb79f64782-1540265251908
Bug Bash Rules:
- Each issue has a dollar value. Dollar values are based upon complexity and priority of issue.
- You can assign any unassigned issue to yourself with a "tcx_OpenForPickup" (first come first serve).
- You must update the label to “tcx_Assigned”, and remove the “tcx_OpenForPickup” label.
- You can only self assign one issue at a time. The nature of it being assigned will indicate if it is not available to anyone else.
- You will fix the ticket as a pull request to the master branch
- Once a ticket is fixed, you should label it "tcx_ReadyForReview" where it will then be verified. If something is still broken, the copilot will comment on the ticket.
- After submitting and tagging "tcx_ReadyForReview" you are eligible to accept another. You can do as many tickets as you want, as long as you follow the rules above.
- If the ticket is fixed properly, your pull request will be merged in, and the ticket will be marked "tcx_FixAccepted".
- If the ticket is “tcx_Feedback”, it should be your first priority to fix the issue.
- When the ticket is closed, payment will be recorded, when we issue the payment the tag will be updated to “tcx_Paid”
- If an assigned task is not done in 24 hours, you will be unassigned from the ticket, and it will be opened back up to the community.
- You can ask questions directly on the ticket comments.
- Bug Bashes are different than Bug Hunts - please make sure to check the contest type in the contest name when registering.
IMPORTANT:
- DO NOT make INDENTATION AND SPACE changes. Please focus on completing challenge Tasks. We need to track your changes so focus only code fixes.
- DO NOT DELETE EXISTING FILES/LIBRARY. Confirm with us if needed.
- RE-TEST AND COMPARE ON all required browsers before you submit
SUBMISSION FLOW
- First, make sure your "dev" branch is ALWAYS UPDATED! We will be pushing new code updates in parallel.
- CREATE NEW BRANCH on related repo with the title format "issues/username/XX" where XX is the number on the GitLab Issue.
- DO NOT FORK into your own repo. you MUST create from our repo. We will reject your submission if you submit from your own repo.
- Start working your fixes in that branch, commit and push to your working repo.
- Once you are satisfied with your fixes, you should label it "tcx_ReadyForReview.
- Next you will send MERGE REQUEST to "dev".
- Put Ticket url you were working on in the Merge Request description.
- If something is still broken, the Reviewer will comment on the ticket. We will update the label as " tcx_Feedback" and you can complete the fixes based on the feedback.
Web Browsers Requirements
Your submission must look and work consistently across these following browsers on the latest versions:
- IE11
- Chrome,
- Edge,
- Safari,
- Firefox