Open aubertc opened 2 years ago
Some examples include:
((a)|('a))+((a)|('a))
(a|'a)\{a}
a|b\{a}
a.b.c.d | 'a.'b.'c.'d
a + ('a | 'b) + b
I have added some other examples in https://github.com/peterbro1/IRDC-CCSK/blob/master/examples/example_processes.md We should use them for tests, and later on, when we look at (bi)simulations.
I am not super familiar with org.junit.jupiter.api.Test
: is there any way of defining a bunch of process objects at the beginning e.g., of the SimulationTest.java , and to use them through the class?
I have tried, using the @Rule
thingy, but couldn't make it work. The idea would be to re-use some of the processes across tests instead of re-defining them for every method in the test class.
I believe this is possible. We could just instantiate an array of processes and use them throughout the class. No need for annotations.
That'd be perfect. Can you get me started?
Sure, would you like to add all the processes listed above? ((a)|('a))+((a)|('a)) (a|'a){a} a|b{a} a.b.c.d | 'a.'b.'c.'d a + ('a | 'b) + b
That'd be a great start, and I'd be happy to complete it, no worries.
Can we create a class of dummy processes, that we would be able to use in tests, but also as "showcase" for the program if needed? This would actually solve the issues as originally stated, along my more particular issue of having a bank of processes to write tests.
It would be nice if the program had either
Or a combination of all of those.