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
Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I have an issue when [...]
Want to add a test suite to the application.
Describe the solution you'd like
A clear and concise description of what you want to happen. Add any considered drawbacks.
As of right now, this issue will remain vague as I don't have a great idea on how I want to structure the test suite. The application is mostly split between separating markup (display logic) from business logic. Because of that, I'm not sure if it'd add much value to test the display logic through unit tests. The business logic seems like a no-brainer for now but I'd like some time to think about and get opinions on what's the best way to write tests that'll add value to the project.
I also want to leverage Cypress for testing as well.
Note: This issue will need to be tackled after issue #29.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Currently n/a
Teachability, Documentation, Adoption, Migration Strategy
If you can, explain how users will be able to use this and possibly write out a version in the docs.
Maybe a screenshot or design?
Currently n/a
The text was updated successfully, but these errors were encountered:
As this issue is essentially a duplicate of issue #30, I'm going to close the issue and add a comment to that issue that remarks on some of the thoughts I brought up here.
Feature Request
Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I have an issue when [...]
Want to add a test suite to the application.
Describe the solution you'd like
A clear and concise description of what you want to happen. Add any considered drawbacks.
As of right now, this issue will remain vague as I don't have a great idea on how I want to structure the test suite. The application is mostly split between separating markup (display logic) from business logic. Because of that, I'm not sure if it'd add much value to test the display logic through unit tests. The business logic seems like a no-brainer for now but I'd like some time to think about and get opinions on what's the best way to write tests that'll add value to the project.
I also want to leverage Cypress for testing as well.
Note: This issue will need to be tackled after issue #29.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Currently n/a
Teachability, Documentation, Adoption, Migration Strategy
If you can, explain how users will be able to use this and possibly write out a version in the docs.
Maybe a screenshot or design?
Currently n/a
The text was updated successfully, but these errors were encountered: