[jira] [Comment Edited] (SUREFIRE-1245) Unable to run TestNG tests using maven surefire plugin.

2016-09-19 Thread Tibor Digana (JIRA)

[ 
https://issues.apache.org/jira/browse/SUREFIRE-1245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15502598#comment-15502598
 ] 

Tibor Digana edited comment on SUREFIRE-1245 at 9/19/16 8:59 AM:
-

I am really not able to find root cause why these tests hang. I am more 
convinced about Selenium timeout issues as I wrote above or problem that 
somebody overrides std/out via {{java.lang.System.setOut(...)}}.
You wrote that:
>>I ran in 2.18 and 2.17 and I am facing the same issue.
This is different from my previous experiences of Surefire running at Mac. 
Other users reported that Surefire 2.19 at Mac hangs but it does not hang in 
2.18.x. This was fixed in 2.19.1. We found only some differences between x86_64 
and Mac that the GC is different, delays and race conditions change and CPU 
cache coherence is different. So I used locks without performance enhancements 
and this was the fix.

Now this issue is different because it does not have these symptoms that 2.18.x 
does not hang. Here every version of Surefire hangs.
In other bugs there was reason why it hanged, because ping feature was 
introduced and bi-directional communication between maven process and forked 
surefire processes in Version 2.19.


was (Author: tibor17):
I am really not able to find root cause why these tests hang. I am more 
convinced about Selenium timeout issues as I wrote above or problem that 
somebody overrides std/out via {{java.lang.System.setOut(...)}}.
You wrote that:
>>I ran in 2.18 and 2.17 and I am facing the same issue.
This is different from my previous experiences of Surefire running at Mac. 
Other users reported that Surefire 2.19 at Mac hangs but it does not hang in 
2.18.x. This was fixed in 2.19.1. We found only some differences between x86_64 
and Mac that the GC is different, delays and race conditions change and CPU 
cache coherence is different. So I used locks without performance enhancements 
and this was the fix.

Now this issue is different because it does not have these symptoms that 2.18.x 
does not hang. Here every version of Surefire hangs.
In other bugs there was reason why it hanged, because ping feature was 
introduced and bi-directional communication between maven process and forked 
surefire processes.

> Unable to run TestNG tests using maven surefire plugin.
> ---
>
> Key: SUREFIRE-1245
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1245
> Project: Maven Surefire
>  Issue Type: Bug
>Reporter: Hemanth
>Assignee: Tibor Digana
>Priority: Blocker
> Attachments: pom.xml, testng.xml
>
>
> I am having testng.xml with around 8 classes. The suite will be running fine 
> but suddenly stops working and gives me unreachable browser exception. The 
> same tests finishes off its execution using failsafe plugin like a charm, but 
> my reporting tool is kind of dependent on the surefire plugin. Running it by 
> testng.xml(Right clicking and clicking on run as testng suite is working fine 
> as well). If there is any mistake that I have done in the pom.xml please help 
> me out as well. Please look into this issue.
> Here is a testng.xml
> 
> http://testng.org/testng-1.0.dtd;>
> 
>  
> 
> 
> 
>   
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
>
>  
>  
> Here is my pom.xml
> 
> http://maven.apache.org/POM/4.0.0;
>  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
>  xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 
> http://maven.apache.org/xsd/maven-4.0.0.xsd;>
> 4.0.0
> 
> ETNA
> inhouse.NewStandardEcommerceTemplate
> 1.0-SNAPSHOT
> 
>   1.8
> 1.5.0.RC2
> 1.8.5
> 2.53.0
>  1.7.7
> 
> ETNA
> New standard ecommerce template
> 
>
> com.fasterxml.jackson.core
> jackson-databind
> 2.7.0
>   
> 
> 
>   com.pojosontheweb
>   monte-repack
>   1.0
>   
> 
>   org.testng
>   testng
>   6.9.10
>   test
> 
> 
> 
> 
>   com.jayway.restassured
>   rest-assured
>   2.9.0
>   
> 
> org.seleniumhq.selenium
> selenium-firefox-driver
> ${version.selenium}
> 
> 
> 
> 
>   org.apache.poi
>   poi
>   3.13
> 
> 
> 
> org.apache.poi
> poi-ooxml
> 3.13
> 
> 
>   org.apache.poi
>   poi-ooxml-schemas
>   3.13
> 
> 
>   
>   org.zeroturnaround
>   zt-zip
>   1.7
>   
>  
> 
>   javax.mail
>   mail
>   1.4.7
> 
> 
> 
> 
> org.seleniumhq.selenium
> selenium-java
> ${version.selenium}
> test
> 
> 
> 
>   org.seleniumhq.selenium
>   

[jira] [Comment Edited] (SUREFIRE-1245) Unable to run TestNG tests using maven surefire plugin.

2016-09-19 Thread Tibor Digana (JIRA)

[ 
https://issues.apache.org/jira/browse/SUREFIRE-1245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15502598#comment-15502598
 ] 

Tibor Digana edited comment on SUREFIRE-1245 at 9/19/16 7:38 AM:
-

I am really not able to find root cause why these tests hang. I am more 
convinced about Selenium timeout issues as I wrote above or problem that 
somebody overrides std/out via {{java.lang.System.setOut(...)}}.
You wrote that:
>>I ran in 2.18 and 2.17 and I am facing the same issue.
This is different from my previous experiences of Surefire running at Mac. 
Other users reported that Surefire 2.19 at Mac hangs but it does not hang in 
2.18.x. This was fixed in 2.19.1. We found only some differences between x86_64 
and Mac that the GC is different, delays and race conditions change and CPU 
cache coherence is different. So I used locks without performance enhancements 
and this was the fix.

Now this issue is different because it does not have these symptoms that 2.18.x 
does not hang. Here every version of Surefire hangs.
In other bugs there was reason why it hanged, because ping feature was 
introduced and bi-directional communication between maven process and forked 
surefire processes.


was (Author: tibor17):
I am really not able to find root cause why these tests hang. I am more 
convinced about Selenium timeout issues as I wrote above or problem that 
somebody overrides std/out via {{java.lang.System.setOut(...)}}.
You wrote that:
>>I ran in 2.18 and 2.17 and I am facing the same issue.
This is different from my previous experiences of Surefire running at Mac. 
Other users reported that Surefire 2.19 at Mac hangs but it does not hang in 
2.18.x. This was fixed in 2.19.1. We found only some differences between x86_64 
and Mac that the GC is different, delays and race conditions change and CPU 
cache coherence is different. So I used locks without performance enhancements 
and this was the fix.

Now this issue is different because it does not have these symptoms that 2.18.x 
does not hang. Here every version of Surefire hangs.
In other bugs there was reason why it hangs, because ping feature was 
introduced and bi-directional communication between maven process and forked 
surefire processes.

> Unable to run TestNG tests using maven surefire plugin.
> ---
>
> Key: SUREFIRE-1245
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1245
> Project: Maven Surefire
>  Issue Type: Bug
>Reporter: Hemanth
>Assignee: Tibor Digana
>Priority: Blocker
> Attachments: pom.xml, testng.xml
>
>
> I am having testng.xml with around 8 classes. The suite will be running fine 
> but suddenly stops working and gives me unreachable browser exception. The 
> same tests finishes off its execution using failsafe plugin like a charm, but 
> my reporting tool is kind of dependent on the surefire plugin. Running it by 
> testng.xml(Right clicking and clicking on run as testng suite is working fine 
> as well). If there is any mistake that I have done in the pom.xml please help 
> me out as well. Please look into this issue.
> Here is a testng.xml
> 
> http://testng.org/testng-1.0.dtd;>
> 
>  
> 
> 
> 
>   
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
>
>  
>  
> Here is my pom.xml
> 
> http://maven.apache.org/POM/4.0.0;
>  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
>  xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 
> http://maven.apache.org/xsd/maven-4.0.0.xsd;>
> 4.0.0
> 
> ETNA
> inhouse.NewStandardEcommerceTemplate
> 1.0-SNAPSHOT
> 
>   1.8
> 1.5.0.RC2
> 1.8.5
> 2.53.0
>  1.7.7
> 
> ETNA
> New standard ecommerce template
> 
>
> com.fasterxml.jackson.core
> jackson-databind
> 2.7.0
>   
> 
> 
>   com.pojosontheweb
>   monte-repack
>   1.0
>   
> 
>   org.testng
>   testng
>   6.9.10
>   test
> 
> 
> 
> 
>   com.jayway.restassured
>   rest-assured
>   2.9.0
>   
> 
> org.seleniumhq.selenium
> selenium-firefox-driver
> ${version.selenium}
> 
> 
> 
> 
>   org.apache.poi
>   poi
>   3.13
> 
> 
> 
> org.apache.poi
> poi-ooxml
> 3.13
> 
> 
>   org.apache.poi
>   poi-ooxml-schemas
>   3.13
> 
> 
>   
>   org.zeroturnaround
>   zt-zip
>   1.7
>   
>  
> 
>   javax.mail
>   mail
>   1.4.7
> 
> 
> 
> 
> org.seleniumhq.selenium
> selenium-java
> ${version.selenium}
> test
> 
> 
> 
>   org.seleniumhq.selenium
>   selenium-server
>   

[jira] [Comment Edited] (SUREFIRE-1245) Unable to run TestNG tests using maven surefire plugin.

2016-09-19 Thread Tibor Digana (JIRA)

[ 
https://issues.apache.org/jira/browse/SUREFIRE-1245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15502598#comment-15502598
 ] 

Tibor Digana edited comment on SUREFIRE-1245 at 9/19/16 7:37 AM:
-

I am really not able to find root cause why these tests hang. I am more 
convinced about Selenium timeout issues as I wrote above or problem that 
somebody overrides std/out via {{java.lang.System.setOut(...)}}.
You wrote that:
>>I ran in 2.18 and 2.17 and I am facing the same issue.
This is different from my previous experiences of Surefire running at Mac. 
Other users reported that Surefire 2.19 at Mac hangs but it does not hang in 
2.18.x. This was fixed in 2.19.1. We found only some differences between x86_64 
and Mac that the GC is different, delays and race conditions change and CPU 
cache coherence is different. So I used locks without performance enhancements 
and this was the fix.

Now this issue is different because it does not have these symptoms that 2.18.x 
does not hang. Here every version of Surefire hangs.
In other bugs there was reason why it hangs, because ping feature was 
introduced and bi-directional communication between maven process and forked 
surefire processes.


was (Author: tibor17):
I am really not able to find root cause why these tests hang. I am more 
convinced about Selenium timeout issues as I wrote above or problem that 
somebody overrides std/out via {{java.lang.System.setOut(...)}}.
You wrote that:
>>I ran in 2.18 and 2.17 and I am facing the same issue.
This is different from my previous experiences of Surefire running at Mac. 
Other users reported that Surefire 2.19 at Mac hangs but it does not hang in 
2.18.x. This was fixed in 2.19.1. We found only one difference between x86_64 
and Mac that the GC is different, delays and race conditions change and CPU 
cache coherence is different. So I used locks without performance enhancements 
and this was the fix.

Now this issue is different because it does not have these symptoms that 2.18.x 
does not hang. Here every version of Surefire hangs.
In other bugs there was reason why it hangs, because ping feature was 
introduced and bi-directional communication between maven process and forked 
surefire processes.

> Unable to run TestNG tests using maven surefire plugin.
> ---
>
> Key: SUREFIRE-1245
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1245
> Project: Maven Surefire
>  Issue Type: Bug
>Reporter: Hemanth
>Assignee: Tibor Digana
>Priority: Blocker
> Attachments: pom.xml, testng.xml
>
>
> I am having testng.xml with around 8 classes. The suite will be running fine 
> but suddenly stops working and gives me unreachable browser exception. The 
> same tests finishes off its execution using failsafe plugin like a charm, but 
> my reporting tool is kind of dependent on the surefire plugin. Running it by 
> testng.xml(Right clicking and clicking on run as testng suite is working fine 
> as well). If there is any mistake that I have done in the pom.xml please help 
> me out as well. Please look into this issue.
> Here is a testng.xml
> 
> http://testng.org/testng-1.0.dtd;>
> 
>  
> 
> 
> 
>   
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
>
>  
>  
> Here is my pom.xml
> 
> http://maven.apache.org/POM/4.0.0;
>  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
>  xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 
> http://maven.apache.org/xsd/maven-4.0.0.xsd;>
> 4.0.0
> 
> ETNA
> inhouse.NewStandardEcommerceTemplate
> 1.0-SNAPSHOT
> 
>   1.8
> 1.5.0.RC2
> 1.8.5
> 2.53.0
>  1.7.7
> 
> ETNA
> New standard ecommerce template
> 
>
> com.fasterxml.jackson.core
> jackson-databind
> 2.7.0
>   
> 
> 
>   com.pojosontheweb
>   monte-repack
>   1.0
>   
> 
>   org.testng
>   testng
>   6.9.10
>   test
> 
> 
> 
> 
>   com.jayway.restassured
>   rest-assured
>   2.9.0
>   
> 
> org.seleniumhq.selenium
> selenium-firefox-driver
> ${version.selenium}
> 
> 
> 
> 
>   org.apache.poi
>   poi
>   3.13
> 
> 
> 
> org.apache.poi
> poi-ooxml
> 3.13
> 
> 
>   org.apache.poi
>   poi-ooxml-schemas
>   3.13
> 
> 
>   
>   org.zeroturnaround
>   zt-zip
>   1.7
>   
>  
> 
>   javax.mail
>   mail
>   1.4.7
> 
> 
> 
> 
> org.seleniumhq.selenium
> selenium-java
> ${version.selenium}
> test
> 
> 
> 
>   org.seleniumhq.selenium
>   selenium-server
>   

[jira] [Comment Edited] (SUREFIRE-1245) Unable to run TestNG tests using maven surefire plugin.

2016-05-21 Thread Hemanth (JIRA)

[ 
https://issues.apache.org/jira/browse/SUREFIRE-1245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15294884#comment-15294884
 ] 

Hemanth edited comment on SUREFIRE-1245 at 5/21/16 10:20 AM:
-

You can clone from bitbucket https://bitbucket.org/hemanthsridhar/etna

File size is too large even after zipping it.

I ran in 2.18 and 2.17 and I am facing the same issue.



was (Author: hemanth.bs):
Hi Tibor. You can clone from bitbucket https://bitbucket.org/hemanthsridhar/etna

> Unable to run TestNG tests using maven surefire plugin.
> ---
>
> Key: SUREFIRE-1245
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1245
> Project: Maven Surefire
>  Issue Type: Bug
>Reporter: Hemanth
>Assignee: Tibor Digana
>Priority: Blocker
> Attachments: pom.xml, testng.xml
>
>
> I am having testng.xml with around 8 classes. The suite will be running fine 
> but suddenly stops working and gives me unreachable browser exception. The 
> same tests finishes off its execution using failsafe plugin like a charm, but 
> my reporting tool is kind of dependent on the surefire plugin. Running it by 
> testng.xml(Right clicking and clicking on run as testng suite is working fine 
> as well). If there is any mistake that I have done in the pom.xml please help 
> me out as well. Please look into this issue.
> Here is a testng.xml
> 
> http://testng.org/testng-1.0.dtd;>
> 
>  
> 
> 
> 
>   
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
>
>  
>  
> Here is my pom.xml
> 
> http://maven.apache.org/POM/4.0.0;
>  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
>  xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 
> http://maven.apache.org/xsd/maven-4.0.0.xsd;>
> 4.0.0
> 
> ETNA
> inhouse.NewStandardEcommerceTemplate
> 1.0-SNAPSHOT
> 
>   1.8
> 1.5.0.RC2
> 1.8.5
> 2.53.0
>  1.7.7
> 
> ETNA
> New standard ecommerce template
> 
>
> com.fasterxml.jackson.core
> jackson-databind
> 2.7.0
>   
> 
> 
>   com.pojosontheweb
>   monte-repack
>   1.0
>   
> 
>   org.testng
>   testng
>   6.9.10
>   test
> 
> 
> 
> 
>   com.jayway.restassured
>   rest-assured
>   2.9.0
>   
> 
> org.seleniumhq.selenium
> selenium-firefox-driver
> ${version.selenium}
> 
> 
> 
> 
>   org.apache.poi
>   poi
>   3.13
> 
> 
> 
> org.apache.poi
> poi-ooxml
> 3.13
> 
> 
>   org.apache.poi
>   poi-ooxml-schemas
>   3.13
> 
> 
>   
>   org.zeroturnaround
>   zt-zip
>   1.7
>   
>  
> 
>   javax.mail
>   mail
>   1.4.7
> 
> 
> 
> 
> org.seleniumhq.selenium
> selenium-java
> ${version.selenium}
> test
> 
> 
> 
>   org.seleniumhq.selenium
>   selenium-server
>   ${version.selenium}
> 
> 
> 
> 
> ru.yandex.qatools.allure
> allure-testng-adaptor
> ${allure.version}
> 
> 
> junit
> junit
> 
> 
> 
>  
> 
> org.hamcrest
> hamcrest-all
> 1.3
> 
> 
>  
>   com.google.code.gson
>   gson
>   2.3.1
>   
>   
>
> org.slf4j
> slf4j-api
> ${version.slf4j}
> test
> 
> 
> 
> org.slf4j
> slf4j-log4j12
> ${version.slf4j}
> test
> 
> 
> 
> org.slf4j
> jul-to-slf4j
> ${version.slf4j}
> test
> 
> 
> 
> org.slf4j
> jcl-over-slf4j
> ${version.slf4j}
> test
> 
> 
> 
> 
> 
>   
>   
> org.apache.maven.plugins
> maven-compiler-plugin
> 3.1
> 
> ${compiler.version}
> ${compiler.version}
> 
> 
>   
> 
> org.apache.maven.plugins
> maven-surefire-plugin
> 2.19.1
> 
>   
>testng.xml
>
> 
> 
> -javaagent:${settings.localRepository}/org/aspectj/aspectjweaver/${aspectj.version}/aspectjweaver-${aspectj.version}.jar
>   

[jira] [Comment Edited] (SUREFIRE-1245) Unable to run TestNG tests using maven surefire plugin.

2016-05-10 Thread Hemanth (JIRA)

[ 
https://issues.apache.org/jira/browse/SUREFIRE-1245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15278201#comment-15278201
 ] 

Hemanth edited comment on SUREFIRE-1245 at 5/10/16 3:51 PM:


I apologise for not attaching before. Here you go. PFA for the attached pom.xml 
and testng.xml 

Please do help me with this issue.


was (Author: hemanth.bs):
I apologise for not attaching before. Here you go. PFA for the attached pom.xml 
and testng.xml 

Please do help me with this issue.

> Unable to run TestNG tests using maven surefire plugin.
> ---
>
> Key: SUREFIRE-1245
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1245
> Project: Maven Surefire
>  Issue Type: Bug
>Reporter: Hemanth
>Priority: Blocker
> Attachments: pom.xml, testng.xml
>
>
> I am having testng.xml with around 8 classes. The suite will be running fine 
> but suddenly stops working and gives me unreachable browser exception. The 
> same tests finishes off its execution using failsafe plugin like a charm, but 
> my reporting tool is kind of dependent on the surefire plugin. Running it by 
> testng.xml(Right clicking and clicking on run as testng suite is working fine 
> as well). If there is any mistake that I have done in the pom.xml please help 
> me out as well. Please look into this issue.
> Here is a testng.xml
> 
> http://testng.org/testng-1.0.dtd;>
> 
>  
> 
> 
> 
>   
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
>
>  
>  
> Here is my pom.xml
> 
> http://maven.apache.org/POM/4.0.0;
>  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
>  xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 
> http://maven.apache.org/xsd/maven-4.0.0.xsd;>
> 4.0.0
> 
> ETNA
> inhouse.NewStandardEcommerceTemplate
> 1.0-SNAPSHOT
> 
>   1.8
> 1.5.0.RC2
> 1.8.5
> 2.53.0
>  1.7.7
> 
> ETNA
> New standard ecommerce template
> 
>
> com.fasterxml.jackson.core
> jackson-databind
> 2.7.0
>   
> 
> 
>   com.pojosontheweb
>   monte-repack
>   1.0
>   
> 
>   org.testng
>   testng
>   6.9.10
>   test
> 
> 
> 
> 
>   com.jayway.restassured
>   rest-assured
>   2.9.0
>   
> 
> org.seleniumhq.selenium
> selenium-firefox-driver
> ${version.selenium}
> 
> 
> 
> 
>   org.apache.poi
>   poi
>   3.13
> 
> 
> 
> org.apache.poi
> poi-ooxml
> 3.13
> 
> 
>   org.apache.poi
>   poi-ooxml-schemas
>   3.13
> 
> 
>   
>   org.zeroturnaround
>   zt-zip
>   1.7
>   
>  
> 
>   javax.mail
>   mail
>   1.4.7
> 
> 
> 
> 
> org.seleniumhq.selenium
> selenium-java
> ${version.selenium}
> test
> 
> 
> 
>   org.seleniumhq.selenium
>   selenium-server
>   ${version.selenium}
> 
> 
> 
> 
> ru.yandex.qatools.allure
> allure-testng-adaptor
> ${allure.version}
> 
> 
> junit
> junit
> 
> 
> 
>  
> 
> org.hamcrest
> hamcrest-all
> 1.3
> 
> 
>  
>   com.google.code.gson
>   gson
>   2.3.1
>   
>   
>
> org.slf4j
> slf4j-api
> ${version.slf4j}
> test
> 
> 
> 
> org.slf4j
> slf4j-log4j12
> ${version.slf4j}
> test
> 
> 
> 
> org.slf4j
> jul-to-slf4j
> ${version.slf4j}
> test
> 
> 
> 
> org.slf4j
> jcl-over-slf4j
> ${version.slf4j}
> test
> 
> 
> 
> 
> 
>   
>   
> org.apache.maven.plugins
> maven-compiler-plugin
> 3.1
> 
> ${compiler.version}
> ${compiler.version}
> 
> 
>   
> 
> org.apache.maven.plugins
> maven-surefire-plugin
> 2.19.1
> 
>   
>testng.xml
>
> 
> 
> -javaagent:${settings.localRepository}/org/aspectj/aspectjweaver/${aspectj.version}/aspectjweaver-${aspectj.version}.jar
> 
> 
> 

[jira] [Comment Edited] (SUREFIRE-1245) Unable to run testNG tests using maven surefire plugin

2016-05-10 Thread Hemanth (JIRA)

[ 
https://issues.apache.org/jira/browse/SUREFIRE-1245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15278201#comment-15278201
 ] 

Hemanth edited comment on SUREFIRE-1245 at 5/10/16 2:45 PM:


I apologise for not attaching before. Here you go. PFA for the attached pom.xml 
and testng.xml 

Please do help me with this issue.


was (Author: hemanth.bs):
I apologise for not attaching before. Here you go. PFA for the attached pom.xml 
and testng.xml 

> Unable to run testNG tests using maven surefire plugin
> --
>
> Key: SUREFIRE-1245
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1245
> Project: Maven Surefire
>  Issue Type: Bug
>Reporter: Hemanth
>Priority: Blocker
> Attachments: pom.xml, testng.xml
>
>
> I am having testng.xml with around 8 classes. The suite will be running fine 
> but suddenly stops working and gives me unreachable browser exception. The 
> same tests finishes off its execution using failsafe plugin like a charm, but 
> my reporting tool is kind of dependent on the surefire plugin. Running it by 
> testng.xml(Right clicking and clicking on run as testng suite is working fine 
> as well). If there is any mistake that I have done in the pom.xml please help 
> me out as well. Please look into this issue.
> Here is a testng.xml
> 
> http://testng.org/testng-1.0.dtd;>
> 
>  
> 
> 
> 
>   
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
>
>  
>  
> Here is my pom.xml
> 
> http://maven.apache.org/POM/4.0.0;
>  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
>  xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 
> http://maven.apache.org/xsd/maven-4.0.0.xsd;>
> 4.0.0
> 
> ETNA
> inhouse.NewStandardEcommerceTemplate
> 1.0-SNAPSHOT
> 
>   1.8
> 1.5.0.RC2
> 1.8.5
> 2.53.0
>  1.7.7
> 
> ETNA
> New standard ecommerce template
> 
>
> com.fasterxml.jackson.core
> jackson-databind
> 2.7.0
>   
> 
> 
>   com.pojosontheweb
>   monte-repack
>   1.0
>   
> 
>   org.testng
>   testng
>   6.9.10
>   test
> 
> 
> 
> 
>   com.jayway.restassured
>   rest-assured
>   2.9.0
>   
> 
> org.seleniumhq.selenium
> selenium-firefox-driver
> ${version.selenium}
> 
> 
> 
> 
>   org.apache.poi
>   poi
>   3.13
> 
> 
> 
> org.apache.poi
> poi-ooxml
> 3.13
> 
> 
>   org.apache.poi
>   poi-ooxml-schemas
>   3.13
> 
> 
>   
>   org.zeroturnaround
>   zt-zip
>   1.7
>   
>  
> 
>   javax.mail
>   mail
>   1.4.7
> 
> 
> 
> 
> org.seleniumhq.selenium
> selenium-java
> ${version.selenium}
> test
> 
> 
> 
>   org.seleniumhq.selenium
>   selenium-server
>   ${version.selenium}
> 
> 
> 
> 
> ru.yandex.qatools.allure
> allure-testng-adaptor
> ${allure.version}
> 
> 
> junit
> junit
> 
> 
> 
>  
> 
> org.hamcrest
> hamcrest-all
> 1.3
> 
> 
>  
>   com.google.code.gson
>   gson
>   2.3.1
>   
>   
>
> org.slf4j
> slf4j-api
> ${version.slf4j}
> test
> 
> 
> 
> org.slf4j
> slf4j-log4j12
> ${version.slf4j}
> test
> 
> 
> 
> org.slf4j
> jul-to-slf4j
> ${version.slf4j}
> test
> 
> 
> 
> org.slf4j
> jcl-over-slf4j
> ${version.slf4j}
> test
> 
> 
> 
> 
> 
>   
>   
> org.apache.maven.plugins
> maven-compiler-plugin
> 3.1
> 
> ${compiler.version}
> ${compiler.version}
> 
> 
>   
> 
> org.apache.maven.plugins
> maven-surefire-plugin
> 2.19.1
> 
>   
>testng.xml
>
> 
> 
> -javaagent:${settings.localRepository}/org/aspectj/aspectjweaver/${aspectj.version}/aspectjweaver-${aspectj.version}.jar
> 
> 
> 
>

[jira] [Comment Edited] (SUREFIRE-1245) Unable to run testNG tests using maven surefire plugin

2016-05-10 Thread Hemanth (JIRA)

[ 
https://issues.apache.org/jira/browse/SUREFIRE-1245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15278201#comment-15278201
 ] 

Hemanth edited comment on SUREFIRE-1245 at 5/10/16 2:43 PM:


I apologise for not attaching before. Here you go. PFA for the attached pom.xml 
and testng.xml 


was (Author: hemanth.bs):
PFA for the attached pom.xml and testng.xml

> Unable to run testNG tests using maven surefire plugin
> --
>
> Key: SUREFIRE-1245
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1245
> Project: Maven Surefire
>  Issue Type: Bug
>Reporter: Hemanth
>Priority: Blocker
> Attachments: pom.xml, testng.xml
>
>
> I am having testng.xml with around 8 classes. The suite will be running fine 
> but suddenly stops working and gives me unreachable browser exception. The 
> same tests finishes off its execution using failsafe plugin like a charm, but 
> my reporting tool is kind of dependent on the surefire plugin. Running it by 
> testng.xml(Right clicking and clicking on run as testng suite is working fine 
> as well). If there is any mistake that I have done in the pom.xml please help 
> me out as well. Please look into this issue.
> Here is a testng.xml
> 
> http://testng.org/testng-1.0.dtd;>
> 
>  
> 
> 
> 
>   
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
>
>  
>  
> Here is my pom.xml
> 
> http://maven.apache.org/POM/4.0.0;
>  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
>  xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 
> http://maven.apache.org/xsd/maven-4.0.0.xsd;>
> 4.0.0
> 
> ETNA
> inhouse.NewStandardEcommerceTemplate
> 1.0-SNAPSHOT
> 
>   1.8
> 1.5.0.RC2
> 1.8.5
> 2.53.0
>  1.7.7
> 
> ETNA
> New standard ecommerce template
> 
>
> com.fasterxml.jackson.core
> jackson-databind
> 2.7.0
>   
> 
> 
>   com.pojosontheweb
>   monte-repack
>   1.0
>   
> 
>   org.testng
>   testng
>   6.9.10
>   test
> 
> 
> 
> 
>   com.jayway.restassured
>   rest-assured
>   2.9.0
>   
> 
> org.seleniumhq.selenium
> selenium-firefox-driver
> ${version.selenium}
> 
> 
> 
> 
>   org.apache.poi
>   poi
>   3.13
> 
> 
> 
> org.apache.poi
> poi-ooxml
> 3.13
> 
> 
>   org.apache.poi
>   poi-ooxml-schemas
>   3.13
> 
> 
>   
>   org.zeroturnaround
>   zt-zip
>   1.7
>   
>  
> 
>   javax.mail
>   mail
>   1.4.7
> 
> 
> 
> 
> org.seleniumhq.selenium
> selenium-java
> ${version.selenium}
> test
> 
> 
> 
>   org.seleniumhq.selenium
>   selenium-server
>   ${version.selenium}
> 
> 
> 
> 
> ru.yandex.qatools.allure
> allure-testng-adaptor
> ${allure.version}
> 
> 
> junit
> junit
> 
> 
> 
>  
> 
> org.hamcrest
> hamcrest-all
> 1.3
> 
> 
>  
>   com.google.code.gson
>   gson
>   2.3.1
>   
>   
>
> org.slf4j
> slf4j-api
> ${version.slf4j}
> test
> 
> 
> 
> org.slf4j
> slf4j-log4j12
> ${version.slf4j}
> test
> 
> 
> 
> org.slf4j
> jul-to-slf4j
> ${version.slf4j}
> test
> 
> 
> 
> org.slf4j
> jcl-over-slf4j
> ${version.slf4j}
> test
> 
> 
> 
> 
> 
>   
>   
> org.apache.maven.plugins
> maven-compiler-plugin
> 3.1
> 
> ${compiler.version}
> ${compiler.version}
> 
> 
>   
> 
> org.apache.maven.plugins
> maven-surefire-plugin
> 2.19.1
> 
>   
>testng.xml
>
> 
> 
> -javaagent:${settings.localRepository}/org/aspectj/aspectjweaver/${aspectj.version}/aspectjweaver-${aspectj.version}.jar
> 
> 
> 
> 
> org.aspectj
> aspectjweaver
>

[jira] [Comment Edited] (SUREFIRE-1245) Unable to run testNG tests using maven surefire plugin

2016-05-10 Thread Tibor Digana (JIRA)

[ 
https://issues.apache.org/jira/browse/SUREFIRE-1245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15277748#comment-15277748
 ] 

Tibor Digana edited comment on SUREFIRE-1245 at 5/10/16 7:41 AM:
-

Please attach effective pom as attached file - not in comment.
We had this problem but it is gone in 2.19.1.
We consider the suites xml file as one test because the TestNG library takes 
over the xml file and we do not control the flow of tests specified in xml.
So it means that your IDE Eclipse, IDEA or whatever tool runs another version 
of TestNG.
Pls check it out again and try to discover errors in TestNG logs which are in 
target folder of particular POM.
It can be that some parent pom has pluginManagement where this plugin has 
nested dependency surefire-testng with older version.


was (Author: tibor17):
Please attach effective pom as attached file - not in comment.
We had this problem but it is gone in 2.19.1.
We consider the suites xml file as one test because the TestNG library takes 
over the xml file and we do not control the flow of tests specified in xml.
So it means that your IDE Eclipse, IDEA or whatever tool runs another version 
of TestNG.
Pls check it out again and try to discover errors in TestNG logs which are in 
target folder of particular POM.
It can be that some parent pom has pluginManagement where this plugin has 
nested dependency surefire-junit4 or surefire-junit47 with older version.

> Unable to run testNG tests using maven surefire plugin
> --
>
> Key: SUREFIRE-1245
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1245
> Project: Maven Surefire
>  Issue Type: Bug
>Reporter: Hemanth
>Priority: Blocker
>
> I am having testng.xml with around 8 classes. The suite will be running fine 
> but suddenly stops working and gives me unreachable browser exception. The 
> same tests finishes off its execution using failsafe plugin like a charm, but 
> my reporting tool is kind of dependent on the surefire plugin. Running it by 
> testng.xml(Right clicking and clicking on run as testng suite is working fine 
> as well). If there is any mistake that I have done in the pom.xml please help 
> me out as well. Please look into this issue.
> Here is a testng.xml
> 
> http://testng.org/testng-1.0.dtd;>
> 
>  
> 
> 
> 
>   
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
>
>  
>  
> Here is my pom.xml
> 
> http://maven.apache.org/POM/4.0.0;
>  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
>  xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 
> http://maven.apache.org/xsd/maven-4.0.0.xsd;>
> 4.0.0
> 
> ETNA
> inhouse.NewStandardEcommerceTemplate
> 1.0-SNAPSHOT
> 
>   1.8
> 1.5.0.RC2
> 1.8.5
> 2.53.0
>  1.7.7
> 
> ETNA
> New standard ecommerce template
> 
>
> com.fasterxml.jackson.core
> jackson-databind
> 2.7.0
>   
> 
> 
>   com.pojosontheweb
>   monte-repack
>   1.0
>   
> 
>   org.testng
>   testng
>   6.9.10
>   test
> 
> 
> 
> 
>   com.jayway.restassured
>   rest-assured
>   2.9.0
>   
> 
> org.seleniumhq.selenium
> selenium-firefox-driver
> ${version.selenium}
> 
> 
> 
> 
>   org.apache.poi
>   poi
>   3.13
> 
> 
> 
> org.apache.poi
> poi-ooxml
> 3.13
> 
> 
>   org.apache.poi
>   poi-ooxml-schemas
>   3.13
> 
> 
>   
>   org.zeroturnaround
>   zt-zip
>   1.7
>   
>  
> 
>   javax.mail
>   mail
>   1.4.7
> 
> 
> 
> 
> org.seleniumhq.selenium
> selenium-java
> ${version.selenium}
> test
> 
> 
> 
>   org.seleniumhq.selenium
>   selenium-server
>   ${version.selenium}
> 
> 
> 
> 
> ru.yandex.qatools.allure
> allure-testng-adaptor
> ${allure.version}
> 
> 
> junit
> junit
> 
> 
> 
>  
> 
> org.hamcrest
> hamcrest-all
> 1.3
> 
> 
>  
>   com.google.code.gson
>   gson
>   2.3.1
>   
>   
>
> org.slf4j
> slf4j-api
> ${version.slf4j}
> test
> 
> 
> 
> org.slf4j
> slf4j-log4j12
> ${version.slf4j}
> test
> 
> 
> 
> org.slf4j
> jul-to-slf4j
> ${version.slf4j}
> test
> 
>

[jira] [Comment Edited] (SUREFIRE-1245) Unable to run testNG tests using maven surefire plugin

2016-05-10 Thread Tibor Digana (JIRA)

[ 
https://issues.apache.org/jira/browse/SUREFIRE-1245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15277748#comment-15277748
 ] 

Tibor Digana edited comment on SUREFIRE-1245 at 5/10/16 7:39 AM:
-

Please attach effective pom as attached file - not in comment.
We had this problem but it is gone in 2.19.1.
We consider the suites xml file as one test because the TestNG library takes 
over the xml file and we do not control the flow of tests specified in xml.
So it means that your IDE Eclipse, IDEA or whatever tool runs another version 
of TestNG.
Pls check it out again and try to discover errors in TestNG logs which are in 
target folder of particular POM.
It can be that some parent pom has pluginManagement where this plugin has 
nested dependency surefire-junit4 or surefire-junit47 with older version.


was (Author: tibor17):
Please attach effective pom as attached file - not in comment.
We had this problem but it is gone in 2.19.1.
We consider the suites xml file as one test because the TestNG library takes 
over the xml file and we do not control the flow of tests specified in xml.
So it means that you IDE Eclipse, IDEA or whatever tool runs another version of 
TestNG.
Pls check it out again and try to discover errors in TestNG logs which are in 
target folder of particular POM.
It can be that some parent pom has pluginManagement where this plugin has 
nested dependency surefire-junit4 or surefire-junit47 with older version.

> Unable to run testNG tests using maven surefire plugin
> --
>
> Key: SUREFIRE-1245
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1245
> Project: Maven Surefire
>  Issue Type: Bug
>Reporter: Hemanth
>Priority: Blocker
>
> I am having testng.xml with around 8 classes. The suite will be running fine 
> but suddenly stops working and gives me unreachable browser exception. The 
> same tests finishes off its execution using failsafe plugin like a charm, but 
> my reporting tool is kind of dependent on the surefire plugin. Running it by 
> testng.xml(Right clicking and clicking on run as testng suite is working fine 
> as well). If there is any mistake that I have done in the pom.xml please help 
> me out as well. Please look into this issue.
> Here is a testng.xml
> 
> http://testng.org/testng-1.0.dtd;>
> 
>  
> 
> 
> 
>   
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
>
>  
>  
> Here is my pom.xml
> 
> http://maven.apache.org/POM/4.0.0;
>  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
>  xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 
> http://maven.apache.org/xsd/maven-4.0.0.xsd;>
> 4.0.0
> 
> ETNA
> inhouse.NewStandardEcommerceTemplate
> 1.0-SNAPSHOT
> 
>   1.8
> 1.5.0.RC2
> 1.8.5
> 2.53.0
>  1.7.7
> 
> ETNA
> New standard ecommerce template
> 
>
> com.fasterxml.jackson.core
> jackson-databind
> 2.7.0
>   
> 
> 
>   com.pojosontheweb
>   monte-repack
>   1.0
>   
> 
>   org.testng
>   testng
>   6.9.10
>   test
> 
> 
> 
> 
>   com.jayway.restassured
>   rest-assured
>   2.9.0
>   
> 
> org.seleniumhq.selenium
> selenium-firefox-driver
> ${version.selenium}
> 
> 
> 
> 
>   org.apache.poi
>   poi
>   3.13
> 
> 
> 
> org.apache.poi
> poi-ooxml
> 3.13
> 
> 
>   org.apache.poi
>   poi-ooxml-schemas
>   3.13
> 
> 
>   
>   org.zeroturnaround
>   zt-zip
>   1.7
>   
>  
> 
>   javax.mail
>   mail
>   1.4.7
> 
> 
> 
> 
> org.seleniumhq.selenium
> selenium-java
> ${version.selenium}
> test
> 
> 
> 
>   org.seleniumhq.selenium
>   selenium-server
>   ${version.selenium}
> 
> 
> 
> 
> ru.yandex.qatools.allure
> allure-testng-adaptor
> ${allure.version}
> 
> 
> junit
> junit
> 
> 
> 
>  
> 
> org.hamcrest
> hamcrest-all
> 1.3
> 
> 
>  
>   com.google.code.gson
>   gson
>   2.3.1
>   
>   
>
> org.slf4j
> slf4j-api
> ${version.slf4j}
> test
> 
> 
> 
> org.slf4j
> slf4j-log4j12
> ${version.slf4j}
> test
> 
> 
> 
> org.slf4j
> jul-to-slf4j
> ${version.slf4j}
> 

[jira] [Comment Edited] (SUREFIRE-1245) Unable to run testNG tests using maven surefire plugin

2016-05-09 Thread Hemanth (JIRA)

[ 
https://issues.apache.org/jira/browse/SUREFIRE-1245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15276807#comment-15276807
 ] 

Hemanth edited comment on SUREFIRE-1245 at 5/9/16 7:29 PM:
---

I think there is some problem with the forkedbooter. Otherwise I don't see any 
other explanation on how my tests work fine in Windows and not in MAC. Running 
the tests by right clicking and run as testng suite works fine as well.


was (Author: hemanth.bs):
I think there is some problem with the forkedbooter. Otherwise I don't see any 
other explanation on how my tests work fine in failsafe plugin. 

> Unable to run testNG tests using maven surefire plugin
> --
>
> Key: SUREFIRE-1245
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1245
> Project: Maven Surefire
>  Issue Type: Bug
>Reporter: Hemanth
>Priority: Blocker
>
> I am having testng.xml with around 8 classes. The suite will be running fine 
> but suddenly stops working and gives me unreachable browser exception. The 
> same tests finishes off its execution using failsafe plugin like a charm, but 
> my reporting tool is kind of dependent on the surefire plugin. Running it by 
> testng.xml(Right clicking and clicking on run as testng suite is working fine 
> as well). If there is any mistake that I have done in the pom.xml please help 
> me out as well. Please look into this issue.
> Here is a testng.xml
> 
> http://testng.org/testng-1.0.dtd;>
> 
>  
> 
> 
> 
>   
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
>
>  
>  
> Here is my pom.xml
> 
> http://maven.apache.org/POM/4.0.0;
>  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
>  xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 
> http://maven.apache.org/xsd/maven-4.0.0.xsd;>
> 4.0.0
> 
> ETNA
> inhouse.NewStandardEcommerceTemplate
> 1.0-SNAPSHOT
> 
>   1.8
> 1.5.0.RC2
> 1.8.5
> 2.53.0
>  1.7.7
> 
> ETNA
> New standard ecommerce template
> 
>
> com.fasterxml.jackson.core
> jackson-databind
> 2.7.0
>   
> 
> 
>   com.pojosontheweb
>   monte-repack
>   1.0
>   
> 
>   org.testng
>   testng
>   6.9.10
>   test
> 
> 
> 
> 
>   com.jayway.restassured
>   rest-assured
>   2.9.0
>   
> 
> org.seleniumhq.selenium
> selenium-firefox-driver
> ${version.selenium}
> 
> 
> 
> 
>   org.apache.poi
>   poi
>   3.13
> 
> 
> 
> org.apache.poi
> poi-ooxml
> 3.13
> 
> 
>   org.apache.poi
>   poi-ooxml-schemas
>   3.13
> 
> 
>   
>   org.zeroturnaround
>   zt-zip
>   1.7
>   
>  
> 
>   javax.mail
>   mail
>   1.4.7
> 
> 
> 
> 
> org.seleniumhq.selenium
> selenium-java
> ${version.selenium}
> test
> 
> 
> 
>   org.seleniumhq.selenium
>   selenium-server
>   ${version.selenium}
> 
> 
> 
> 
> ru.yandex.qatools.allure
> allure-testng-adaptor
> ${allure.version}
> 
> 
> junit
> junit
> 
> 
> 
>  
> 
> org.hamcrest
> hamcrest-all
> 1.3
> 
> 
>  
>   com.google.code.gson
>   gson
>   2.3.1
>   
>   
>
> org.slf4j
> slf4j-api
> ${version.slf4j}
> test
> 
> 
> 
> org.slf4j
> slf4j-log4j12
> ${version.slf4j}
> test
> 
> 
> 
> org.slf4j
> jul-to-slf4j
> ${version.slf4j}
> test
> 
> 
> 
> org.slf4j
> jcl-over-slf4j
> ${version.slf4j}
> test
> 
> 
> 
> 
> 
>   
>   
> org.apache.maven.plugins
> maven-compiler-plugin
> 3.1
> 
> ${compiler.version}
> ${compiler.version}
> 
> 
>   
> 
> org.apache.maven.plugins
> maven-surefire-plugin
> 2.19.1
> 
>   
>testng.xml
>
> 
> 
> 

[jira] [Comment Edited] (SUREFIRE-1245) Unable to run testNG tests using maven surefire plugin

2016-05-09 Thread Hemanth (JIRA)

[ 
https://issues.apache.org/jira/browse/SUREFIRE-1245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15275748#comment-15275748
 ] 

Hemanth edited comment on SUREFIRE-1245 at 5/9/16 10:55 AM:


If you see my pom I am using the latest version of surefire. This is
happening only in MAC.. I ran the same code in Windows and it is working
fine. In MAC if all my @Test are in one class only then SOMETIMES it will work. 
If they are distributed different classes then it stops execution after a while 
providing
unreachable browser exception.
If I use failsafe plugin it is working fine.(In MAC)
Again this is happening only in MAC. Surefire(the same code) is working fine in 
windows.


was (Author: hemanth.bs):
If you see my pom I am using the latest version of surefire. This is
happening only in mac.. I ran the same code in Windows and it is working
fine. In mac if all my @Test are in one class only then it will work. If it
is in a different class then it stops execution after a while providing
unreachable browser exception.
If I use failsafe plugin it is working fine.
Again this is happening only in mac. Surefire(the same code) is working fine in 
windows.

> Unable to run testNG tests using maven surefire plugin
> --
>
> Key: SUREFIRE-1245
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1245
> Project: Maven Surefire
>  Issue Type: Bug
>Reporter: Hemanth
>Priority: Blocker
>
> I am having testng.xml with around 8 classes. The suite will be running fine 
> but suddenly stops working and gives me unreachable browser exception. The 
> same tests finishes off its execution using failsafe plugin like a charm, but 
> my reporting tool is kind of dependent on the surefire plugin. Running it by 
> testng.xml(Right clicking and clicking on run as testng suite is working fine 
> as well). If there is any mistake that I have done in the pom.xml please help 
> me out as well. Please look into this issue.
> Here is a testng.xml
> 
> http://testng.org/testng-1.0.dtd;>
> 
>  
> 
> 
> 
>   
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
>
>  
>  
> Here is my pom.xml
> 
> http://maven.apache.org/POM/4.0.0;
>  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
>  xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 
> http://maven.apache.org/xsd/maven-4.0.0.xsd;>
> 4.0.0
> 
> ETNA
> inhouse.NewStandardEcommerceTemplate
> 1.0-SNAPSHOT
> 
>   1.8
> 1.5.0.RC2
> 1.8.5
> 2.53.0
>  1.7.7
> 
> ETNA
> New standard ecommerce template
> 
>
> com.fasterxml.jackson.core
> jackson-databind
> 2.7.0
>   
> 
> 
>   com.pojosontheweb
>   monte-repack
>   1.0
>   
> 
>   org.testng
>   testng
>   6.9.10
>   test
> 
> 
> 
> 
>   com.jayway.restassured
>   rest-assured
>   2.9.0
>   
> 
> org.seleniumhq.selenium
> selenium-firefox-driver
> ${version.selenium}
> 
> 
> 
> 
>   org.apache.poi
>   poi
>   3.13
> 
> 
> 
> org.apache.poi
> poi-ooxml
> 3.13
> 
> 
>   org.apache.poi
>   poi-ooxml-schemas
>   3.13
> 
> 
>   
>   org.zeroturnaround
>   zt-zip
>   1.7
>   
>  
> 
>   javax.mail
>   mail
>   1.4.7
> 
> 
> 
> 
> org.seleniumhq.selenium
> selenium-java
> ${version.selenium}
> test
> 
> 
> 
>   org.seleniumhq.selenium
>   selenium-server
>   ${version.selenium}
> 
> 
> 
> 
> ru.yandex.qatools.allure
> allure-testng-adaptor
> ${allure.version}
> 
> 
> junit
> junit
> 
> 
> 
>  
> 
> org.hamcrest
> hamcrest-all
> 1.3
> 
> 
>  
>   com.google.code.gson
>   gson
>   2.3.1
>   
>   
>
> org.slf4j
> slf4j-api
> ${version.slf4j}
> test
> 
> 
> 
> org.slf4j
> slf4j-log4j12
> ${version.slf4j}
> test
> 
> 
> 
> org.slf4j
> jul-to-slf4j
> ${version.slf4j}
> test
> 
> 
> 
> org.slf4j
> jcl-over-slf4j
> ${version.slf4j}
> test
> 
> 
> 
> 
> 
>   
>   
> org.apache.maven.plugins
> 

[jira] [Comment Edited] (SUREFIRE-1245) Unable to run testNG tests using maven surefire plugin

2016-05-09 Thread Hemanth (JIRA)

[ 
https://issues.apache.org/jira/browse/SUREFIRE-1245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15275748#comment-15275748
 ] 

Hemanth edited comment on SUREFIRE-1245 at 5/9/16 10:41 AM:


If you see my pom I am using the latest version of surefire. This is
happening only in mac.. I ran the same code in Windows and it is working
fine. In mac if all my @Test are in one class only then it will work. If it
is in a different class then it stops execution after a while providing
unreachable browser exception.
If I use failsafe plugin it is working fine.
Again this is happening only in mac. Surefire(the same code) is working fine in 
windows.


was (Author: hemanth.bs):
If you see my pom I am using the latest version of surefire. This is
happening only in mac.. I ran the same code in Windows and it is working
fine. In mac if all my @Test are in one class only then it will work. If it
is in a different class then it stops execution after a while providing
unreachable browser exception.
If I use failsafe plugin it is working fine.
Again this is happening only in mac. Surefire is working fine in windows.

https://issues.apache.org/jira/browse/SUREFIRE-1245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15275687#comment-15275687
]
influence of Selenium, etc.
fine but suddenly stops working and gives me unreachable browser exception.
The same tests finishes off its execution using failsafe plugin like a
charm, but my reporting tool is kind of dependent on the surefire plugin.
Running it by testng.xml(Right clicking and clicking on run as testng suite
is working fine as well). If there is any mistake that I have done in the
pom.xml please help me out as well. Please look into this issue.
http://maven.apache.org/xsd/maven-4.0.0.xsd;>
 
-javaagent:${settings.localRepository}/org/aspectj/aspectjweaver/${aspectj.version}/aspectjweaver-${aspectj.version}.jar
 
${project.build.directory}/site/allure-maven-plugin


> Unable to run testNG tests using maven surefire plugin
> --
>
> Key: SUREFIRE-1245
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1245
> Project: Maven Surefire
>  Issue Type: Bug
>Reporter: Hemanth
>Priority: Blocker
>
> I am having testng.xml with around 8 classes. The suite will be running fine 
> but suddenly stops working and gives me unreachable browser exception. The 
> same tests finishes off its execution using failsafe plugin like a charm, but 
> my reporting tool is kind of dependent on the surefire plugin. Running it by 
> testng.xml(Right clicking and clicking on run as testng suite is working fine 
> as well). If there is any mistake that I have done in the pom.xml please help 
> me out as well. Please look into this issue.
> Here is a testng.xml
> 
> http://testng.org/testng-1.0.dtd;>
> 
>  
> 
> 
> 
>   
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
>
>  
>  
> Here is my pom.xml
> 
> http://maven.apache.org/POM/4.0.0;
>  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
>  xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 
> http://maven.apache.org/xsd/maven-4.0.0.xsd;>
> 4.0.0
> 
> ETNA
> inhouse.NewStandardEcommerceTemplate
> 1.0-SNAPSHOT
> 
>   1.8
> 1.5.0.RC2
> 1.8.5
> 2.53.0
>  1.7.7
> 
> ETNA
> New standard ecommerce template
> 
>
> com.fasterxml.jackson.core
> jackson-databind
> 2.7.0
>   
> 
> 
>   com.pojosontheweb
>   monte-repack
>   1.0
>   
> 
>   org.testng
>   testng
>   6.9.10
>   test
> 
> 
> 
> 
>   com.jayway.restassured
>   rest-assured
>   2.9.0
>   
> 
> org.seleniumhq.selenium
> selenium-firefox-driver
> ${version.selenium}
> 
> 
> 
> 
>   org.apache.poi
>   poi
>   3.13
> 
> 
> 
> org.apache.poi
> poi-ooxml
> 3.13
> 
> 
>   org.apache.poi
>   poi-ooxml-schemas
>   3.13
> 
> 
>   
>   org.zeroturnaround
>   zt-zip
>   1.7
>   
>  
> 
>   javax.mail
>   mail
>   1.4.7
> 
> 
> 
> 
> org.seleniumhq.selenium
> selenium-java
> ${version.selenium}
> test
> 
> 
> 
>   org.seleniumhq.selenium
>   selenium-server
>   ${version.selenium}
> 
> 
> 
> 
> ru.yandex.qatools.allure
> allure-testng-adaptor
> ${allure.version}
> 
> 
> junit
> junit
> 
> 
> 
>  
> 
> org.hamcrest
>