Unfortunately that didn't work either. Probably I'm missing something important. QaModule doesn't even seem to be loaded on startup.
On Wed, Aug 6, 2014 at 9:44 PM, Ilya Obshadko <[email protected]> wrote: > I'm running the test using 'mvn test'. That's why I expect all system > properties defined in the maven-surefire-plugin section to be available > at runtime. > > But contributing them using QaModule makes sense, I'll try that. > > > On Wed, Aug 6, 2014 at 6:19 PM, Lance Java <[email protected]> > wrote: > >> AFAIK the page tester does not reference web.xml. Depending how you are >> running your test, it might not "see" the jar manifest generated by >> pom.xml >> either (if the classes are on the classpath rather than the jar). >> >> You might need to use the second PageTester constructor where you >> explicitly pass an array of Module classes rather than relying on the jar >> manifest / web.xml. You could create an extra TestModule for your symbols >> (or use System properties). >> On 6 Aug 2014 05:45, "Ilya Obshadko" <[email protected]> wrote: >> >> > I'm trying to set up QA execution mode for unit & integration tests with >> > TestNG, using PageTester. >> > >> > Upon test launch, I receive the following error: >> > >> > [2014-08-06 08:37:56,272] [ERROR] [Registry] Symbol 'my.custom.symbol' >> is >> > not defined. >> > >> > Not sure what's wrong here: this symbol is defined in both web.xml (as >> > context parameter) and pom.xml (as a system property >> > in maven-surefire-plugin configuration). >> > >> > Thanks for any suggestions. >> > >> > -- >> > Ilya Obshadko >> > >> > > > > -- > Ilya Obshadko > > -- Ilya Obshadko
