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
I am planning to release veza@1.0.0 very soon, but before I do so, I want to ensure full functionality for all developers, for which we will need a test suite.
Currently, the code is tested in "parts" inside test files, then once they are working correctly, they are implemented into the code. A downside of this is, it does not test the implementation (or at least, not fully). And having one would definitely increase the speed of development since I will be able to automatize the tests and run them anytime with a single command, as opposed to editing some examples and test with them.
The text was updated successfully, but these errors were encountered:
Describe the proposal
I am planning to release
veza@1.0.0very soon, but before I do so, I want to ensure full functionality for all developers, for which we will need a test suite.Currently, the code is tested in "parts" inside test files, then once they are working correctly, they are implemented into the code. A downside of this is, it does not test the implementation (or at least, not fully). And having one would definitely increase the speed of development since I will be able to automatize the tests and run them anytime with a single command, as opposed to editing some examples and test with them.
The text was updated successfully, but these errors were encountered: