Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Telling tests with duplicate names apart
See original GitHub issuePrinters like beforeEach and passed accept test names which specify the tests. When using this technique it’s not always possible to tell the tests apart, e.g. when tests don’t have a name at all (thus, null is passed to printers) or duplicate names are allowed and used.
From a glance, passing FlatTest instances instead of the names could solve this problem as it’d be possible to inspect the inner TestCode fields and the test names would still be accessible as well. However, it’s possible to use the same test code inside different test cases so still leaves a chance of ambiguity. It seems assigning a unique id to each flat test in toTestCodeList could solve it. Another printer accepting a list of flat tests to run could be added as well.
If we’re to change the printers and flat tests this way it’d be quite a serious breaking change, though, it seems it could fix all ambiguities in printers.
Issue Analytics
- State:
- Created 4 years ago
- Comments:11 (11 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
You mean feedback on Expecto support, when it arrives, right? It’s probably going to appear in a some later EAP build (we haven’t shipped any for 2019.3 yet actually), I’ll be eager to get it then. I’ll let you know when there’s anything to test available. 😉
Do you want to get feedback? I have rider installed, and am obviously using Expecto.