What’s new in our product?
What’s happening? You can now edit descriptions of your tests.
What’s the benefit for you? Your tests are consequently more reader-friendly. Your team can jump into your tests and understand their functional behaviour in seconds.
It will also help you identify which test failed when running Jest from command-line.
How does it work? You’ll notice a new “Test Description” option in the column selector :
What’s happening? You can now build your test assertions based on a subset of objects.
What’s the benefit for you? With this upgrade, it becomes even easier to build tests on (very) complex objects. You can now build very accurate and precise tests on objects without worrying about how complex those objects might be.
How does it work? The option to add some subset keys in the object option is now accessible once you click the column selector :
Check the subset you have just created and the matching column will be added in the expectations section of your Tests / Suggestions
Returned and expected values
What’s happening? We refactored our UI in order to provide a clear distinction between your tests’ returned values and their expected values.
How does it work? If your test fails, the Ponicode extension will display the returned value (the one making the test fail) against the expected value.
Two options are available to you:
1/ Fix your code in order to pass the test => wise choice, no new bugs and no more broken production in sight. Damn, that test was useful.
2/ Fix your test in one click. Update the expected value by clicking on the icon => easy peasy lemon squeezy
Unit testing has never been so simple!
We hope you’ll enjoy our update. Don’t hesitate to share your feedback with us so we can keep on improving the tool and match your user’s needs.START PONICODE