I know that right now, I am attacking a few items ...
# testingl
lmajano
07/18/2022, 7:43 PMI know that right now, I am attacking a few items directly:
• Known bugs
• Performance
• Ability to do dry runs, so it can be used by IDEs and CLI
• WireBox integration to support Modules
• New testing UI experiences
• And new VSCode extension which is partially finalized that will support jumping, highlighting, running, etc
• Inline Datasets for iteration and calling
• Some new matchers (toStartWith, toEndWith, and(), when(), unless() )
• Skipping function (skip (message ) )
• Localized before/afterAll by Suites
d
danmurphy
07/19/2022, 4:47 AM+1 for dry run for sure. I'm assuming that means I'd be able to browse the test suite without running them? Similar to the current test browser, but going all the way to the test level, not just file level?
danmurphy
07/19/2022, 5:10 AMAdmittedly sparse on details here, but one more thing. I’d love to run tests in parallel. I know there is the asyncAll parameter in the describe block, but I’ve never been able to get it to work (but haven’t spent time digging into it). Usually the 2nd test in a suite nearly always fails for some reason or another. Is the async stuff pretty bullet proof? Is this most likely our own code’s fault?
We mostly write integration tests and so our tests take forever to run. It’d be awesome if they were truly running in parallel. So yell at me if it is for sure my own fault somehow. 😄
l
lmajano
07/20/2022, 3:09 PMrunning things in parallel is always tricky, because, technically we can spawn the threads no problem
lmajano
07/20/2022, 3:09 PMthe issue is tracking everything async
lmajano
07/20/2022, 3:09 PMyour app needs to support it
lmajano
07/20/2022, 3:09 PMmocking gets in the way because youa re mocking a running app
lmajano
07/20/2022, 3:09 PMetc
lmajano
07/20/2022, 3:09 PMThere is no easy switch here
lmajano
07/20/2022, 3:10 PMunless you use http calls
2 Views