You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In looking over our codebase recently, I discovered that our tests on SceptrePlan are downright bad. Test coverage is poor, it doesn't really test all the functionality, and they're not very easy to read or maintain.
Ideally, we would have tests that cover all "public" methods of the class and validate the expected outcomes against the actual outcomes.
This is a very useful, low-risk opportunity for those looking to contribute to Sceptre.
The text was updated successfully, but these errors were encountered:
jfalkenstein
changed the title
The tests for SceptrePlan are pretty terrible and could use being completely redone.
The tests for SceptrePlan are pretty terrible and could use being completely redone
Jul 24, 2022
You can add me as an assignee, not sure how much bandwidth I have vs how much workload there is but I can at least start with taking a stab at breaking this out into chunks. Any help/paired programming sessions would definitely be appreciated :)
@ericabrauer I would be inclined to close this issue unless you are still working on it? We all know that the tests aren't perfect, but without Jon here to help, it seems unlikely it could get prioritised.
In looking over our codebase recently, I discovered that our tests on SceptrePlan are downright bad. Test coverage is poor, it doesn't really test all the functionality, and they're not very easy to read or maintain.
Ideally, we would have tests that cover all "public" methods of the class and validate the expected outcomes against the actual outcomes.
This is a very useful, low-risk opportunity for those looking to contribute to Sceptre.
The text was updated successfully, but these errors were encountered: