I am just trying to follow the getting started tutorial and have run into some unexpected issues while creating a simple scenario on Mac OSX.
I created a project and was following the example for creating a simple scenario (google search on "Pablo Picasso".) I got through steps 1 & 2 (inserting & renaming business workflow) with no problem.
Step 3 (implement workflow) initially gave me some trouble, as the provided documentation has some incorrect information in this step. The instructions call for the user to press "Crtl+1", but on a Mac it should be "Cmd+1". Is the documentation bundled with the demo version of Twist OS-specific to the version that I chose to download?
However, it was in steps 4 & 5 that I really got stuck. Upon clicking Cmd+1 on the individual workflow steps I was given a choice of creating or recording; I assumed that creating was the correct choice (there was no mention of this option in the tutorial.) Then, I copied and pasted the code supplied in the tutorial, as instructed. The result is code that would seem to have multiple markers that need to be resolved for each line. (As an aside, I am not a scripter. I am approaching this evaluation from more of the business user perspective. However, I would like to think that I can follow the instructions given in the turorial with no problems provided that I am supplied with the requisite code.)
I have provided a screen shot displaying the code and the associated warning messages. The image should also show the expanded warning message for the first line of offending code. Any help that can be provided would be greatly appreciated.
Comment
Hello,
Could you please provide the said screenshot?
Thank you,
Srijayanth
Interesting, I was experiencing what appeared to be the same problem on MacOSx and Twist 2.2 and following the Getting Started Tutorial.
While the screen shot looks like the Junit classes weren't being found even though they showed up in the project libraries... but after reading closely, I noticed the import statement should be:
import static junit.framework.Assert.*;
and not
import static org.junit.framework.Assert.*;
After that, the compile errors went away.