question

amichaels avatar image
amichaels asked amichaels answered

iTest can't find a test case file

We are running itestcli from a jenkins job. The first step is an svn checkout of all the projects, and then we execute itestcli. From time to time, we see the following error: `"12:27:36 Fail exec 3.8.2 3.8.2 main Fail to load test case: Test case file "project:[link text][1]//automation/testCases/probe/L1TrafficTest.fftc" does not exist."` I've attached the complete Jenkins output. You can see that the files have been checked out, but iTest can't seem to find them. [1]: /storage/temp/4190-jenkins_files.zip
iTestiTest Enterpriseitestclievcicontinuous integration
jenkins_files.zip (371.7 KiB)
10 |950

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

amichaels avatar image
amichaels answered
I found that one cause of this error is that if there exists a .project file in the workspace folder, this throws off all of the project URIs. Delete the .project file in the workspace folder, and everything should work normally.
10 |950

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

gretztx avatar image
gretztx answered amichaels commented
Could this be a timing issue? After the check-out iTest must to a "refresh" ... right? Maybe the refresh hadn't completed by the time you run the test.
1 comment
10 |950

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

amichaels avatar image amichaels ♦ commented ·
I think this might be resolved by using the -rw flag with itestcli. The refresh of the workspace should pick up the new files added since last execution. I'm wondering if this will kick off a workspace rebuild.
0 Likes 0 ·
amichaels avatar image
amichaels answered
I thought about that. I'm not sure what the timing requirements are, or what causes the workspace build, or how to check the progress of the workspace build :( For the immediate future, it looks like there was a path issue. The SVN checkout apparently added another level of directory, but I'm not so sure this was the true cause of the problem. I also have an open question on the workspace build mechanism. http://forums.spirent.com/questions/22398/under-what-conditions-does-itestcli-rebuild-a-work.html
10 |950

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

amichaels avatar image
amichaels answered amichaels edited
Apparently this was related to a known issue in the SVNkit plugin for Jenkins. We have moved to using the svn command line executable and have not seen any more issues like this.
10 |950

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Write an Answer

Hint: Notify or tag a user in this post by typing @username.

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.