Challenge Overview
Challenge Overview
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ IMPORTANT ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Once claimed issues have to be completed and PR provided during 24 HOURS in this Bug Bash
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Challenge Objectives
Convert a known list of PyRunner tests to run in the pyTest framework instead.
VM Note
Note that this bug bash will require users to use a Virtual Machine (VM). This VM is provided as a VMWare image and requires relatively significant hardware resources. By default, it's set for 4 CPUs and 16GB RAM. You may be able to run it with less, but that isn't something we're going to support, so please make sure you have beefy hardware to run the VM. This is a commercial project, so you should use a properly licensed version of VMWare workstation.Project Background
The client has a large number of PyRunner tests that are going to be converted to the pyTest framework. This challenge will be one in a series of bug bashes to convert the individual tests. There will be a number of similar challenges, so this is a good chance to get familiar with the work so you're prepared for future challenges!Individual requirements
NOTE: You MUST follow the specific guidelines in the README.md file in the Gitlab repository. Make sure that your new test executes as described in the `Executing a PyTest test`, and that you follow the guidelines outlined in `Notes on test conversion`
In this challenge, you can pick up issues listed on Gitlab and accomplish them within 24 hours to get the prizes which are mentioned in the issues titles.
Please, read the rules carefully:
You can pick up any issue which has a label “tcx_OpenForPickup”:
- Important! Also, check comments on the issue that nobody asked to be assigned to this issue yet.
- If the issue is not open for pick up but the previous participant asked to unassign him, it’s allowed to claim the issue.
- If you see that previous participant didn’t complete an issue within 24 hours, it’s not allowed to claim the issue until the participant asks to be unassigned in comments, or issue is marked as open for pick up by the copilot.
To start working on an issue ask in the Gitlab comments to assign the issue to youself.
- Start working on the issue without waiting to be assigned, your comment with an intention to work on the issue is enough. But make sure, by reloading the page, that nobody has asked to be assigned the issue before you.
- After you’ve asked for the assignment, time starts and the issue has to be completed and a PR provided within 24 hours.
- If you need more time to complete the issue, post a comment with an explanation, otherwise, the ticket could be marked as open for pickup.
If you don’t want to finish the issue, please ask in the comments to be unassigned from the issue.
- Note, if a participant has asked to be unassigned from the issue, another participant can ask to be assigned to the issue in comments and directly start working on it without waiting to be assigned. Also, in this case, it doesn't matter if the issue has label tcx_OpenForPickup or not.
You can work only on one issue at a time.
- Fix the issue and create a pull request to the develop branch.
- When you submit the PR, make another comment at the issue like “It’s done and ready for review” or similar and provide a link to the PR. Please also apply label `tcx_ReadyForReview`. Follow the issue for the possible comments from the project team. You can now start working on the next ticket (no need to wait for the review to finish).
- If the ticket is fixed properly, your pull request will be merged in, and the ticket will be marked as "tcx_FixAccepted". When the ticket is closed, payment will be recorded, and ticket tagged "tcx_Paid".
- You'll be required to fix any merge conflicts before the change is reviewed and merged.
List of issues
Bug Bash issues
https://gitlab.com/tc-eaton/unit-test-migration/issues
Please ignore the prize shown in this challenge, that is just the estimated purse from all the tickets.
For this Bug Bash, we will be paying per accepted fix based on the prize amount noted in each issue's title.
Final Submission Guidelines
Create a PR against develop branch. Note, to create a PR you will need to fork the repository.