Stuck on an issue?
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.
some test case names not unique
See original GitHub issueNon-unique test names are inconvenient since it requires printing the whole path in order to distinguish test cases in results. For instance, the name callcallcallcode_001 is used for three different test cases: stCallCodes, stCallDelegateCodesCallCodeHomestead, and stCallDelegateCodesHomestead.
Issue Analytics
- State:
- Created 6 years ago
- Comments:5
Top Results From Across the Web
JUnit test names are not unique #2025 - GitHub
As a stopgap solution we could append an incrementing number to each test case name in case of duplicates. All reactions.
Read more >Unique Test Names - NCrunch Documentation
This includes test names that are automatically derived from theory or test case parameters. Test names that are not unique between tests or...
Read more >How to Write Effective Test Case Names (With Examples)
Be concise. Test case names are usually limited to a specific length, so space is at a premium. Make sure to keep names...
Read more >Robot framework ensure unique test case name
I would like, in my suite setup line, to go through each of the test case names, and make sure none of them...
Read more >Use unique names for tests best practice | CodeReview.doctor
Duplicate names for tests results in some tests being skipped. When a function or class is defined multiple times in the same scope...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
thats because of a copypaste that was used back when those tests were created. Actually I suppose that now with generalStateTests we could merge some copied tests back together. (but that would requie a lot of work)
as for the test names. you could manually rename such tests. there are so many tests in those test cases so I didn’t bother with the test names from some point. the tests are all combinations of call callcode delegatecall between themselves
The problem was is copy paste. We actually need to review tests and rename same tests. (Different folder, same name)