Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Catch2 SECTIONs to TextExplorer test list #66

Closed
BlackZork opened this issue Feb 28, 2019 · 8 comments
Closed

Add Catch2 SECTIONs to TextExplorer test list #66

BlackZork opened this issue Feb 28, 2019 · 8 comments
Labels
enhancement New feature or request v4.x Expected to be addressed in the next major release

Comments

@BlackZork
Copy link

Is your feature request related to a problem? Please describe.
It is hard to debug single catch2 SECTION

Describe the solution you'd like
Show list of TEST_CASE SECTIONs in Test Explorer panel. Allow to run and debug single section.

Describe alternatives you've considered
If it is hard to add next level to TestExplorer tree it would be great if TEST_CASE and its SECTIONs could be displayed next to each other on single list.

@matepek
Copy link
Owner

matepek commented Feb 28, 2019

The Catch2 framework doesn't support it. :/
See this issue for details.

What I could do to generate the executable parameter list for the failing sections. Then it would be easy to set up a launch configuration for the executable.

Would you use it?

@matepek
Copy link
Owner

matepek commented Mar 1, 2019

I made something for you (like 👵 makes 🍪). It will be released soon in version > 2.3.21
Tell me how you like it.

@BlackZork
Copy link
Author

BlackZork commented Mar 1, 2019

Thanks. Now I manually edit cmake launch configuration when debugging a section. OTOH I replaced most of my sections with test cases, it is much easier to run them from TestExplorer.

@matepek
Copy link
Owner

matepek commented Mar 1, 2019

You have to run the test beforehand you debug it.
If you use windows or linux, I wouldn't mind a screenshot about the new feature. Curious about how it looks like on those platforms.

@matepek matepek closed this as completed Mar 1, 2019
@Trass3r
Copy link

Trass3r commented Jun 8, 2021

The sections do get reported in the xml output.
Could the test tree maybe be updated to include the sections after the tests are run?

@matepek
Copy link
Owner

matepek commented Jun 8, 2021

Yes. In version 4.x it will be able to.
It's on the roadmap but life is just a little bit busier than usual. (In a good way :)

@Trass3r
Copy link

Trass3r commented Jun 8, 2021

Nice!
One thing to keep in mind for the implementation is that generators aren't well integrated.
For me it doesn't report generated values like sections so I get multiple copies of the same subtree.
So especially when trying to run individual sections this may become confusing.

@matepek matepek added enhancement New feature or request v4.x Expected to be addressed in the next major release labels Jun 9, 2021
@matepek matepek reopened this Jun 9, 2021
@matepek
Copy link
Owner

matepek commented Nov 22, 2021

Dear User,

Version 4+ has been released recently.

It is still missing

Allow to run and debug single section.

but it is on the todo list and I will look into it.

I'm closing this issue for now. If you disagree then please comment !open.

@matepek matepek closed this as completed Nov 22, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request v4.x Expected to be addressed in the next major release
Projects
None yet
Development

No branches or pull requests

3 participants