Related to the Hacktoberfest Welcome ticket: https://github.com/neomjs/neo/issues/5963 (Please read this ticket first)
This is a shout-out to all automated Testers out there.
We already started to write unit tests for the vdom engine, collections and the custom class config system:
https://github.com/neomjs/neo/tree/dev/test/siesta/tests
We also created a couple of component tests using Siesta 5:
https://github.com/neomjs/neo/tree/dev/test/components
Nick @canonic-epicure, the creator of the Siesta Testing Tool, did create a PoC for Siesta 6:
https://github.com/neomjs/neo/tree/siesta6/test/siesta6 (all unit tests work)
Siesta v6 is a super nice project which is using PlayWright to generate headless browsers:
https://github.com/bryntum/siesta
The PoC for component based testing in v6 is still missing (we might need Nicks help on this one).
Inside the hacktoberfest scope, this would be worth a lot of PRs => at least one for each component (also, one for basic testing of one component and additional PRs for more advanced tests). As a follow-up, we could also automatically test examples & demo apps.
Please let me know, in case anyone is interested in writing more tests, especially for the component library. This would help us a lot with avoiding future regression bugs.
Thanks and best regards,
Tobi
Related to the Hacktoberfest Welcome ticket: https://github.com/neomjs/neo/issues/5963 (Please read this ticket first)
This is a shout-out to all
automated Testersout there.We already started to write unit tests for the vdom engine, collections and the custom class config system: https://github.com/neomjs/neo/tree/dev/test/siesta/tests
We also created a couple of component tests using Siesta 5: https://github.com/neomjs/neo/tree/dev/test/components
Nick @canonic-epicure, the creator of the Siesta Testing Tool, did create a PoC for Siesta 6: https://github.com/neomjs/neo/tree/siesta6/test/siesta6 (all unit tests work)
Siesta v6 is a super nice project which is using PlayWright to generate headless browsers: https://github.com/bryntum/siesta
The PoC for component based testing in v6 is still missing (we might need Nicks help on this one).
Inside the hacktoberfest scope, this would be worth a lot of PRs => at least one for each component (also, one for basic testing of one component and additional PRs for more advanced tests). As a follow-up, we could also automatically test examples & demo apps.
Please let me know, in case anyone is interested in writing more tests, especially for the component library. This would help us a lot with avoiding future regression bugs.
Thanks and best regards, Tobi