2015-05-04 93 views
2

我在TestNG中尝试了一些硬和软断言的例子,而softassertions按预期工作,我面临硬断言的问题。TestNG中的硬和软断言

根据我从互联网上读取的信息 - 如果硬断言失败,它不执行其他测试。

下面的代码printTest3()测试应该被跳过,因为ffPageElementsTestHardAssert()失败。可有一个人帮助我理解这个behavior..Thanks

@BeforeTest 
    public void beforeTest() { 
     DOMConfigurator.configure("log4j.xml"); 

     TestBase.startBrowser("firefox","http://newtours.demoaut.com/index.php"); 
     Assert.assertEquals(TestBase.getBasePageTitle(), "Welcome: Mercury Tours"); 
     driver.manage().window().maximize();   
     APP_LOGS.info("Page displayed"); 
     lp = PageFactory.initElements(driver, LoginPage.class); 
     ffPage = lp.doLogin("test", "test"); 
     sa = new SoftAssert(); 
    } 


    @Test(priority = 2) 
    public void ffPageElementsTestHardAssert() { 
    Assert.assertTrue(ffPage.ff_Type_oneway.isDisplayed()); 
    Assert.assertTrue(ffPage.ff_Type_roundtrip.isDisplayed()); 
    Assert.assertTrue(ffPage.ff_PassengerCount.isDisplayed()); 
    Assert.assertTrue(ffPage.ff_DepartingFrom.isDisplayed()); 
    Assert.assertTrue(ffPage.ff_DepartingMonth.isDisplayed()); 
    Assert.assertTrue(ffPage.ff_DepartingDay.isDisplayed()); 
    Assert.assertTrue(ffPage.ff_ArrivingIn.isDisplayed()); 
    Assert.assertTrue(ffPage.ff_ReturningMonth.isDisplayed()); 
    Assert.assertTrue(ffPage.ff_ReturningDay.isDisplayed()); 
    Assert.assertTrue(ffPage.ff_ServiceClass_EC.isDisplayed()); 
    Assert.assertTrue(ffPage.ff_ServiceClass_BC.isDisplayed()); 
    Assert.assertTrue(ffPage.ff_ServiceClass_FC.isDisplayed()); 
    Assert.assertTrue(ffPage.ff_Airline.isDisplayed()); 
    Assert.assertTrue(ffPage.ff_Continue.isDisplayed()); 
    } 


    @Test(priority = 1) 
    public void printTest1(){ 
     Assert.assertEquals(5, 5); 
    } 

    @Test(priority = 3) 
    public void printTest3(){ 
     System.out.println("Hello3"); 
    } 



    Output: 
    ------- 
    Hello3 
    PASSED: printTest1 
    PASSED: printTest3 
    FAILED: ffPageElementsTestHardAssert 
    org.openqa.selenium.NoSuchElementException: Unable to locate element: {"method":"name","selector":"airlin"} 
    Command duration or timeout: 65 milliseconds 
    For documentation on this error, please visit: http://seleniumhq.org/exceptions/no_such_element.html 
    Build info: version: '2.43.1', revision: '5163bce', time: '2014-09-10 16:27:58' 
    System info: host: 'PSHYS0091', ip: '10.233.18.60', os.name: 'Windows 7', os.arch: 'amd64', os.version: '6.1', java.version: '1.7.0_51' 
    Session ID: da04681e-4918-4d75-94ee-ff590464c7c5 
    Driver info: org.openqa.selenium.firefox.FirefoxDriver 
    Capabilities [{platform=WINDOWS, databaseEnabled=true, cssSelectorsEnabled=true, javascriptEnabled=true, acceptSslCerts=true, handlesAlerts=true, browserName=firefox, webStorageEnabled=true, nativeEvents=true, rotatable=false, locationContextEnabled=true, applicationCacheEnabled=true, takesScreenshot=true, version=31.6.0}] 
     at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) 
     at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source) 
     at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source) 
     at java.lang.reflect.Constructor.newInstance(Unknown Source) 
     at org.openqa.selenium.remote.ErrorHandler.createThrowable(ErrorHandler.java:204) 
     at org.openqa.selenium.remote.ErrorHandler.throwIfResponseFailed(ErrorHandler.java:156) 
     at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:599) 
     at org.openqa.selenium.remote.RemoteWebDriver.findElement(RemoteWebDriver.java:352) 
     at org.openqa.selenium.remote.RemoteWebDriver.findElementByName(RemoteWebDriver.java:425) 
     at org.openqa.selenium.By$ByName.findElement(By.java:299) 
     at org.openqa.selenium.remote.RemoteWebDriver.findElement(RemoteWebDriver.java:344) 
     at org.openqa.selenium.support.pagefactory.DefaultElementLocator.findElement(DefaultElementLocator.java:59) 
     at org.openqa.selenium.support.pagefactory.internal.LocatingElementHandler.invoke(LocatingElementHandler.java:37) 
     at com.sun.proxy.$Proxy8.isDisplayed(Unknown Source) 
     at com.nt.tests.FlightFinderTest.ffPageElementsTestHardAssert(FlightFinderTest.java:74) 
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
     at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) 
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) 
     at java.lang.reflect.Method.invoke(Unknown Source) 
     at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:84) 
     at org.testng.internal.Invoker.invokeMethod(Invoker.java:714) 
     at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:901) 
     at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1231) 
     at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:127) 
     at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:111) 
     at org.testng.TestRunner.privateRun(TestRunner.java:767) 
     at org.testng.TestRunner.run(TestRunner.java:617) 
     at org.testng.SuiteRunner.runTest(SuiteRunner.java:334) 
     at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:329) 
     at org.testng.SuiteRunner.privateRun(SuiteRunner.java:291) 
     at org.testng.SuiteRunner.run(SuiteRunner.java:240) 
     at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52) 
     at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86) 
     at org.testng.TestNG.runSuitesSequentially(TestNG.java:1224) 
     at org.testng.TestNG.runSuitesLocally(TestNG.java:1149) 
     at org.testng.TestNG.run(TestNG.java:1057) 
     at org.testng.remote.RemoteTestNG.run(RemoteTestNG.java:111) 
     at org.testng.remote.RemoteTestNG.initAndRun(RemoteTestNG.java:204) 
     at org.testng.remote.RemoteTestNG.main(RemoteTestNG.java:175) 
    Caused by: org.openqa.selenium.NoSuchElementException: Unable to locate element: {"method":"name","selector":"airlin"} 
    For documentation on this error, please visit: http://seleniumhq.org/exceptions/no_such_element.html 
    Build info: version: '2.43.1', revision: '5163bce', time: '2014-09-10 16:27:58' 
    System info: host: 'PSHYS0091', ip: '10.233.18.60', os.name: 'Windows 7', os.arch: 'amd64', os.version: '6.1', java.version: '1.7.0_51' 



    =============================================== 
     Default test 
     Tests run: 3, Failures: 1, Skips: 0 
    =============================================== 


    =============================================== 
    Default suite 
    Total tests run: 3, Failures: 1, Skips: 0 

回答

5

主要区别是:

HardAssert - 抛出AssertException立即测试标记为失败和测试套件继续下一@Test

SoftAssert - 在@Test期间收集错误(不会引发异常),并且如果您致​​电org.testng.asserts.SoftAssert#assertAll@Test的末尾如果有任何和测试套件再次抛出异常继续下一步@Test

+0

谢谢Jaroslav ...如果我有一组断言在一个测试,如果我的第一个断言失败,测试中的其他断言将不会执行? – skumar

+1

的确,如果硬断言失败,其他断言将不会被执行,并且测试立即失败。如果软断言失败,则所有其他软断言都将被执行,并且在测试结束时,您必须调用assertAll来检查结果(它类似于所有软断言的一个硬断言) –

+0

一个观察:如果存在断言错误,则SoftAssert将继续下一个断言,并将在最后抛出错误并继续下一次测试,但是如果有例外,例如;元素未找到异常,那么它将不会继续下一个断言。我可以使用try..catch来克服这个,有没有其他方法? – skumar