Challenge Overview
Challenge Objectives
- Bash bugs identified in the previous bug-hunt challenge
Project Background
Karma is a Javascript test runner, you can use Karma to run your tests by choosing either Jasmine or Mocha as the testing framework. They are an essential part of modern software development because they allow the developer to write tests before the actual code for the feature or defects under development. The tests are committed to the repo along with the project source files. These tests are executed by the CI/ CD system to verify that the integrated code works as designed (or at least as far as it is tested). Other developers run these tests while they are coding and before deployment. If any of these checks fail during development, work halts and the focus switches to fixing the failed test. This new approach has lead to the continuous integration of software on a daily or even hourly basis. For this reason, it is imperative that the testing experience is integrated into the developer's process. Microsoft's VS code is a lightweight developer IDE that is free and has a robust ecosystem of extensions. The goal of this challenge is to create a Karma vscode extension with similar functionality as the Karma Webstorm plugin. We have run many challenges to create this VSCode extension:
- Create Test Explorer: http://www.topcoder.com/challenge-details/30069929/?type=develop&noncache=true
- Create Test Explorer Part 2: http://www.topcoder.com/challenge-details/30070440/?type=develop&noncache=true
- Implement Coverage: http://www.topcoder.com/challenge-details/30070660/?type=develop&noncache=true
- Support Angular Projects: http://www.topcoder.com/challenge-details/30072384/?type=develop&noncache=true
- We also run many f2f tasks to make the extension support the NX Angular projects as well.
We will also offer $100 bonus to the developer fixed the most number of bugs.
Technology Stack
- VSCode extension
- Karma
- Angular 4+
- Nx: https://nrwl.io/nx/
Code Access
- karma vscode gitlab repo access will be granted in the forum.
- 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 VSCode Extension
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.
SUBMISSION FLOW
- First, make sure your "develop" branch is ALWAYS UPDATED! We will be pushing new code updates in parallel.
- Fork our respository
- Once you are satisfied with your fixes, you should label it "tcx_ReadyForReview.
- Send merge request, 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.