|
|
|
|
|
Re: Parameterized unit test [message #1726873 is a reply to message #1726821] |
Thu, 17 March 2016 08:22 |
Mihai Traistariu Messages: 6 Registered: March 2016 |
Junior Member |
|
|
Thank you very much for your answers.
@Thomas : I could use list() but I would like to have one test for each file, to see complete results and have more flexibility
@Anton : This was my idea as well, to write my own runner. I will give it a try starting from your example. Although, I thing there should be a better solution, this is why I started this thread.
@Christian/Moritz : Yes, I saw the deprecated API of "org.eclipse.xtext.junit4.parameterized" package and I saw it points to Xpect. But I didn't find a detailed tutorial and an example of a parameterized test (or something similar). Can you please give me an example and/or point me to a tutorial to see how it is recommended to structure the projects when working with Xpect ?
[Updated on: Thu, 17 March 2016 09:34] Report message to a moderator
|
|
|
|
Re: Parameterized unit test [message #1792817 is a reply to message #1792815] |
Tue, 24 July 2018 11:08 |
Elie Richa Messages: 72 Registered: February 2016 |
Member |
|
|
Ok I actually just found the solution myself...
It turns out adding org.junit.runners.parameterized to the Import-Package section of MANIFEST.MF solves both the build and run problems. I'm not sure what the semantics of Import-Package is and why it happens to fix the problem, but it does. So there you go, for future encounters of that issue :)
Cheers
Elie Richa, Ph.D
Software Engineer, AdaCore
https://www.adacore.com
|
|
|
Powered by
FUDForum. Page generated in 0.03629 seconds