[GODRIVER-2100] Audit and improve the existing test suite Created: 21/Jul/21 Updated: 21/Dec/22 Resolved: 01/Dec/22 |
|
| Status: | Closed |
| Project: | Go Driver |
| Component/s: | Testing |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Epic | Priority: | Minor - P4 |
| Reporter: | Benji Rewis (Inactive) | Assignee: | Benji Rewis (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | size-medium | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Quarter: | FY23Q4 |
| Documentation Changes: | Not Needed |
| Start date: |
| Description |
SummaryWith the creation of a new testing policy, we should give some attention to our testing suite. This epic contains a number of testing QOL improvements and tasks. The following is a subset of the tasks in the epic and their potential improvements to the driver. Improving the testing suite will make development on the Go driver both faster and of higher quality.
MotivationWho is the affected end user?Developers contributing to the Go driver. How does this affect the end user?The testing suite has some inconsistencies and key areas for improvement. Is this issue urgent?Evaluating the performance of our driver has come up recently and being more clear in/adherent to our testing policy is important. Is this ticket required by a downstream team?No. Is this ticket only for tests?Yes. |
| Comments |
| Comment by Rachelle Palmer [ 21/Dec/22 ] |
|
|
| Comment by PM Bot [ 27/Jan/22 ] |
|
If you are not logged in, you can view the tickets in this epic by following this link. |
| Comment by PM Bot [ 19/Jan/22 ] |
|
If you are not logged in, you can view the tickets in this epic by following this link. |