this would work only IF the providers integrated with surefire properly which is not the case the side effect is that integrating a provider such as testng (which only works with surefire last time i checked) creates integration exceptions NONE of these integration exceptions would occur IF the testng codebase was merged into surefire any integration exceptions would be discovered in the surefire packaging phase before deployment comments? Martin Gainty ______________________________________________ Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni.
> From: [email protected] > Date: Mon, 23 Nov 2009 18:57:58 -0800 > Subject: Re: merging testng into surefire.. > To: [email protected] > > I do not think I fully understand the different 'Provider' concept, but if > you are looking to run different types of tests in 1 suite, then you could > create a separate PROFILE in Maven, then your suite could have something > like: > > <!DOCTYPE suite SYSTEM "http://testng.org/testng-1.0.dtd";> > <suite name="Functional_TestNG" verbose="1"> > > *<parameter name="providerType" value="${provider.type}" />* > <parameter name="application-address" value=" > http://localhost:8889/webapp/"; / > > <test name="Service Tests - Generic"> > <packages> > <package name="com.baselogic.service" /> > </packages> > </test> > ... > > Or you could hard code them per test section: > > <test name="Service Tests - ProviderTypeA"> > * <parameter name="providerType" value="A" />* > <packages> > <package name="com.baselogic.service" /> > </packages> > </test> > > <test name="Service Tests - ProviderTypeB"> > * <parameter name="providerType" value="B" />* > <packages> > <package name="com.baselogic.service" /> > </packages> > </test> > > Is this what you mean? > > > --- > Thank You… > > Mick Knutson, President > > BASE Logic, Inc. > Enterprise Architecture, Design, Mentoring & Agile Consulting > p. (866) BLiNC-411: (254-6241-1) > f. (415) 685-4233 > > Website: http://baselogic.com > Linked IN: http://linkedin.com/in/mickknutson > Vacation Rental: http://tahoe.baselogic.com > --- > > > > On Mon, Nov 23, 2009 at 6:46 PM, Martin Gainty <[email protected]> wrote: > > > > > i understand paul's assertion for a separate provider suite > > > > but how would this suite of packages work? > > once constructed is there a way to construct integration tests to prevent > > potential version mismatch between provider and surefire? > > > > Thanks! > > Martin > > > > > From: [email protected] > > > Date: Mon, 23 Nov 2009 18:06:06 -0800 > > > Subject: Re: merging testng into surefire.. > > > To: [email protected] > > > > > > You can create a suite of Packages instead of defining each class to make > > > the suite easier at 1st. > > > > > > --- > > > Thank You… > > > > > > Mick Knutson, President > > > > > > BASE Logic, Inc. > > > Enterprise Architecture, Design, Mentoring & Agile Consulting > > > p. (866) BLiNC-411: (254-6241-1) > > > f. (415) 685-4233 > > > > > > Website: http://baselogic.com > > > Linked IN: http://linkedin.com/in/mickknutson > > > Vacation Rental: http://tahoe.baselogic.com > > > --- > > > > > > > > > > > > On Mon, Nov 23, 2009 at 5:42 PM, Martin Gainty <[email protected]> > > wrote: > > > > > > > > > > > Good Evening All- > > > > > > > > org.apache.maven.surefire.booter.SurefireExecutionException: > > > > org.testng.xml.Parser.parse()Lorg/testng/xml/XmlSuite;; nested > > exception is > > > > java.lang.NoSuchMethodError: > > > > org.testng.xml.Parser.parse()Lorg/testng/xml/XmlSuite; > > > > java.lang.NoSuchMethodError: > > > > org.testng.xml.Parser.parse()Lorg/testng/xml/XmlSuite; > > > > at > > > > > > org.apache.maven.surefire.testng.TestNGXmlTestSuite.locateTestSets(TestNGXmlTestSuite.java:132) > > > > at > > > > > > org.apache.maven.surefire.Surefire.createSuiteFromDefinition(Surefire.java:150) > > > > > > > > as you can see Surefire createSuiteFromDefinition method calls to > > testng > > > > which calls a nonexistent parse() routine which if corrrect would > > return an > > > > array XmlSuite > > > > > > > > these integration scenarios could be fleshed out more easily if > > surefire > > > > completely merged the testng codebase. > > > > > > > > Eventually i will find a parse routine that works from testng TestSuite > > if > > > > not i will of course code the missing method > > > > > > > > im wondering if testng should be merged completely into surefire to > > avert > > > > these types of integration errors > > > > > > > > any viable reasons to keep testng as completely separate project from > > sure? > > > > Martin Gainty > > > > ______________________________________________ > > > > Verzicht und Vertraulichkeitanmerkung/Note de déni et de > > confidentialité > > > > > > > > Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene > > > > Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede > > unbefugte > > > > Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese > > Nachricht > > > > dient lediglich dem Austausch von Informationen und entfaltet keine > > > > rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von > > > > E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. > > > > Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas > > le > > > > destinataire prévu, nous te demandons avec bonté que pour satisfaire > > > > informez l'expéditeur. N'importe quelle diffusion non autorisée ou la > > copie > > > > de ceci est interdite. Ce message sert à l'information seulement et > > n'aura > > > > pas n'importe quel effet légalement obligatoire. Étant donné que les > > email > > > > peuvent facilement être sujets à la manipulation, nous ne pouvons > > accepter > > > > aucune responsabilité pour le contenu fourni. > > > > > > > > > > > > > > > > _________________________________________________________________ > > > > Windows 7: It works the way you want. Learn more. > > > > > > > > > > http://www.microsoft.com/Windows/windows-7/default.aspx?ocid=PID24727::T:WLMTAGL:ON:WL:en-US:WWL_WIN_evergreen:112009v2 > > > > _________________________________________________________________ > > Bing brings you maps, menus, and reviews organized in one place. > > > > http://www.bing.com/search?q=restaurants&form=MFESRP&publ=WLHMTAG&crea=TEXT_MFESRP_Local_MapsMenu_Resturants_1x1 _________________________________________________________________ Windows 7: I wanted simpler, now it's simpler. I'm a rock star. http://www.microsoft.com/Windows/windows-7/default.aspx?h=myidea?ocid=PID24727::T:WLMTAGL:ON:WL:en-US:WWL_WIN_myidea:112009
