Sed 's|skipfailedinvocationcounts|skipfailedinvocationCounts|g'ĥ) Confirmed that the tweaks were applied:ĭiff 118301772.cache rw-r-r- 1 nikolaos staff 6841 Jun 15 14:34 118301772.cacheĤ) Ran the following commands to tweak the downloaded DTD rw-r-r- 1 nikolaos staff 800 Jun 15 14:20 cache.xml Nikolaos (mac0) ~/home/sw/company/.metadata/.plugins/ Workspace which is rooted at: ~/home/sw/company Have it download the DTD again so that I would know that it was in theīatch of the newest things (actually I used fgrep on the string we areģ) Tracked the caches to the following hidden folders under my project Procedure of what I did in case others need it:ġ) I cleared the cache for the TestNG DTD and then did a Maven Test to It downloads into cache files (not separate files with their actual So this wasn't so difficult except that MyEclipse stuffs things that > "skipfailedinvocationcounts" to "skipfailedinvocationCounts" to keep > it would use your own version of the DTD, and in that DTD, you would rename > Nikolaos: in the meantime, you could try to configure your environment so On Jun 15, 3:57 pm, Cédric Beust ♔ wrote: Sorry again for the trouble, and please let me know if at least for now, this fixes your problem. (it might be a problem with the TestNG plug-in, we can look into this in a separate discussion). Having said that, you should probably try to understand why Eclipse cannot find the internal version of the DTD because pinging a web server for each TestNG run is a bit overkill. You should see invocation-numbers in that file now and this should solve your problem. I just updated the version on the web site, and you can see for yourself by pointing your browser to (this HTML version is a dynamic view of the real file, i.e. It looks like in your case, Eclipse can't find that DTD internally and instead, it's going to the web site, which might explain why you're having this problem. TestNG uses an internal resolver so that it should always use the one inside the jar file and never have to go to the web site. I updated the testng-1.0.dtd file inside the distribution but not the one on the web site ( ) so I'm very sorry about that. I added this attribute in the latest version of TestNG. Example file below and to be clear the "invocation-numbers"Īttribute is what Eclipse complains about. Is there not an updated DTD or something? I tried 1.1 but it doesĪny idea how to properly resolve this issue anyone? ohhhh yeah "some" last test failed.ĭeleting the Test-Output folder clears things up but then that just "Problems" view that the new code just added does not contain an error Immediately obvious - without constantly flipping back to the Eclipse on each node all the way up to the parent and it is not This is VERY problematic while developing because Eclipse marks a red Project as the 1.0 DTD for testng-failed.xml does not include the However, when a test fails we get an unexpected "Error" in our Eclipse We are using TestNG 5.12 and Surefire report plugin 2.5 in a MyEclipseĨ.5 project and heavily utilize testing to inject and After doing a fair amount of research I have yet to resolve this
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |