ttt307307 / junitparams

Automatically exported from code.google.com/p/junitparams
0 stars 0 forks source link

Cannot run individual parameter test case. #44

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. Run Test class.
2. List of cases will be displayed on junit console.
3. Select and run/debug a specific parameter test case.

What is the expected output? 
Specific parameter test case will run. 

What do you see instead?
The input type of the launch configuration does not exist.

What version of the product are you using? On what operating system?
Eclipse Indigo SR2, Windows 7 64-bit. junitparams 1.01.

Please provide any additional information below.

Original issue reported on code.google.com by royce....@gmail.com on 7 Jun 2013 at 3:19

Attachments:

GoogleCodeExporter commented 8 years ago
Just as a point of note, the JUnit Parameterized runner supports this to an 
extent (The name of the test method in this example is "compute"):
- Right-click on the top-level test listing (the one without "compute" in the 
screenshot), and you can't "Go to File"
- Right-click on the nested case (the one starting with "compute") and you can 
double-click to open the test, as well as running or debugging the specific case

The Parameterized runner derives from Suite instead of BlockJUnit4ClassRunner, 
so there are some differences in the implementation logic; with luck, you can 
extrapolate from there.

Hope this helps!

Original comment by michael....@gmail.com on 21 Jun 2013 at 6:04

Attachments:

GoogleCodeExporter commented 8 years ago
Thank you Michael for looking into my issue and for sharing this beautiful 
testing library.  Will try this again when I have access to my work.  More 
power to you.

Original comment by royce....@gmail.com on 22 Jun 2013 at 10:47

GoogleCodeExporter commented 8 years ago
For now this is not doable. It's related to the way how eclipse tries to find 
the double-clicked element and how junit handles naming of test methods and 
classes.

Original comment by lipinski...@gmail.com on 26 Oct 2013 at 4:08