-
Bug
-
Resolution: Unresolved
-
Minor
-
None
-
System OS Environment
===================
MAC OS X EL Capitan (Ver.10.11.4)
Testing Application Environment
=========================
System#1 - Jenkins (Ver. 1.651.1) + Testopia Plugin (Ver. 1.3) + Java (Ver. 1.8.0_91) + Appium (Ver. 1.5.2) + Android Studio (Ver. 2.1) + GitHub Client Plugin (Ver. 1.19.6) + Git Plugin (Ver. 2.4.4) + GitHub Plugin (1.18.2)
System#2 - Bugzilla (Ver. 4.4.11) + Testopia (Ver. 2.5)System OS Environment =================== MAC OS X EL Capitan (Ver.10.11.4) Testing Application Environment ========================= System#1 - Jenkins (Ver. 1.651.1) + Testopia Plugin (Ver. 1.3) + Java (Ver. 1.8.0_91) + Appium (Ver. 1.5.2) + Android Studio (Ver. 2.1) + GitHub Client Plugin (Ver. 1.19.6) + Git Plugin (Ver. 2.4.4) + GitHub Plugin (1.18.2) System#2 - Bugzilla (Ver. 4.4.11) + Testopia (Ver. 2.5)
System OS Environment
===================
MAC OS X EL Capitan (Ver.10.11.4)
Testing Application Environment
=========================
System#1 - Jenkins (Ver. 1.651.1) + Testopia Plugin (Ver. 1.3) + Java (Ver. 1.8.0_91) + Appium (Ver. 1.5.2) + Android Studio (Ver. 2.1) + GitHub Client Plugin (Ver. 1.19.6) + Git Plugin (Ver. 2.4.4) + GitHub Plugin (Ver. 1.18.2)
System#2 - Bugzilla (Ver. 4.4.11) + Testopia (Ver. 2.5)
=======================================================================
ISSUE:
(1) My system#1 on Jenkins is unable to mark/update test cases on my other system#2 (installed with Bugzilla-Testopia) via the Testopia plugin
(2) Jenkins always return "Found 0 test results" on the console output even though there are test results configured in System#2 Bugzilla-Testopia
Feel free to contact me via email or Skype -> chowkeljin@hotmail.com if you need more info
=======================================================================
SETUP:
This environment setup, is basically to automate testing for mobile apps on Android. Jenkins gets my app code from GitHub, compiles my app code into an android apk file, and then runs my app with my TestNG scripts on the Android AVD emulator. Finally, the TestNG results are returned back to Jenkins.
The setup of my 2 systems are as follows:
----------------------------------------------------------------------------------------------
System#1 - Jenkins (Ver. 1.651.1) + Testopia Plugin (Ver. 1.3) + Java (Ver. 1.8.0_91) + Appium (Ver. 1.5.2) + Android Studio (Ver. 2.1) + GitHub Client Plugin (Ver. 1.19.6) + Git Plugin (Ver. 2.4.4) + GitHub Plugin (1.18.2)
- Jenkins is installed with Testopia 1.3 plugin
- Jenkins is connected to Testopia via http://localhost/bugzilla/xmlrpc.cgi
- In Jenkins, for the Project Configuration, under Testopia Configuration, my settings are as follows:
----------------------------------------------------------------------------------------------
>Test Execution
>Single Test Build Steps
>Execute Shell
>Command:
cd /Users/Shared/Jenkins/Home/workspace/testHello/Hello
chmod +x gradlew
sudo ./gradlew assembleRelease
cd /Users/xxxi/eclipse/Workspace/HelloTest
export classpath=.:/Users/xxx/eclipse/Workspace/HelloTest/lib/selenium-server-standalone-2.53.0.jar
sudo java -cp /Users/xxx/eclipse/Workspace/HelloTest/lib/selenium-server-standalone-2.53.0.jar:bin org.testng.TestNG testng.xml
----------------------------------------------------------------------------------------------
>Publish TestNG Results
>TestNG XML report pattern
**/testng-results.xml
----------------------------------------------------------------------------------------------
>Test Result Seeking Strategies:
>TestNG method name
>Include Pattern:
**/testng-results.xml
=====================================================
System#2 - Bugzilla (Ver. 4.4.11) + Testopia (Ver. 2.5)
Bugzilla is installed on Apache 2.4 and connected to a MySQL database named 'bugs'.
I have created 1 x Test Product, 1 x Test Plan, 1 x Test Case and a 1 x Test Run for capturing the results.
=======================================================================
OUTPUT FROM JENKINS
Started by user xxx
Building in workspace /Users/Shared/Jenkins/Home/workspace/testHello
> git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
> git config remote.origin.url https://github.com/xxx/testrepository.git # timeout=10
Fetching upstream changes from https://github.com/xxx/testrepository.git
> git --version # timeout=10
using .gitcredentials to set credentials
> git config --local credential.username xxx@xxx.com # timeout=10
> git config --local credential.helper store --file=/Users/Shared/Jenkins/tmp/git5846547902386590390.credentials # timeout=10
> git -c core.askpass=true fetch --tags --progress https://github.com/xxx.xxx.git +refs/heads/:refs/remotes/origin/
> git config --local --remove-section credential # timeout=10
> git rev-parse refs/remotes/origin/master^
> git rev-parse refs/remotes/origin/origin/master^{commit}
# timeout=10
Checking out Revision 2a232e840d0a4650f87b266dd39fe52fb6e04e3e (refs/remotes/origin/master)
> git config core.sparsecheckout # timeout=10
> git checkout -f 2a232e840d0a4650f87b266dd39fe52fb6e04e3e
> git rev-list 2a232e840d0a4650f87b266dd39fe52fb6e04e3e # timeout=10
Connecting to Testopia to retrieve automated test cases
Executing single build steps
[testHello] $ /bin/sh -xe /Users/Shared/Jenkins/tmp/hudson1632792907636290656.sh
+ cd /Users/Shared/Jenkins/Home/workspace/testHello/Hello
+ chmod +x gradlew
+ sudo ./gradlew assembleRelease
Incremental java compilation is an incubating feature.
:app:preBuild UP-TO-DATE
:app:preReleaseBuild UP-TO-DATE
:app:checkReleaseManifest
:app:preDebugBuild UP-TO-DATE
:app:prepareComAndroidSupportAnimatedVectorDrawable2330Library UP-TO-DATE
:app:prepareComAndroidSupportAppcompatV72330Library UP-TO-DATE
:app:prepareComAndroidSupportSupportV42330Library UP-TO-DATE
:app:prepareComAndroidSupportSupportVectorDrawable2330Library UP-TO-DATE
:app:prepareReleaseDependencies
:app:compileReleaseAidl UP-TO-DATE
:app:compileReleaseRenderscript UP-TO-DATE
:app:generateReleaseBuildConfig UP-TO-DATE
:app:generateReleaseAssets UP-TO-DATE
:app:mergeReleaseAssets UP-TO-DATE
:app:generateReleaseResValues UP-TO-DATE
:app:generateReleaseResources UP-TO-DATE
:app:mergeReleaseResources UP-TO-DATE
:app:processReleaseManifest UP-TO-DATE
:app:processReleaseResources UP-TO-DATE
:app:generateReleaseSources UP-TO-DATE
:app:compileReleaseJavaWithJavac UP-TO-DATE
:app:compileReleaseNdk UP-TO-DATE
:app:compileReleaseSources UP-TO-DATE
:app:lintVitalRelease
:app:prePackageMarkerForRelease
:app:transformClassesWithDexForRelease UP-TO-DATE
:app:mergeReleaseJniLibFolders UP-TO-DATE
:app:transformNative_libsWithMergeJniLibsForRelease UP-TO-DATE
:app:processReleaseJavaRes UP-TO-DATE
:app:transformResourcesWithMergeJavaResForRelease UP-TO-DATE
:app:packageRelease UP-TO-DATE
:app:assembleRelease
BUILD SUCCESSFUL
Total time: 19.673 secs
This build could be faster, please consider using the Gradle Daemon: https://docs.gradle.org/2.10/userguide/gradle_daemon.html
+ cd /Users/xxx/eclipse/Workspace/HelloTest
+ export classpath=.:/Users/xxx/eclipse/Workspace/HelloTest/lib/selenium-server-standalone-2.53.0.jar
+ classpath=.:/Users/xxx/eclipse/Workspace/HelloTest/lib/selenium-server-standalone-2.53.0.jar
+ sudo java -cp /Users/xxx/eclipse/Workspace/HelloTest/lib/selenium-server-standalone-2.53.0.jar:bin org.testng.TestNG testng.xml
[TestNG] Running:
/Users/xxx/eclipse/Workspace/HelloTest/testng.xml
PASSED: testHello
===============================================
Default test
Tests run: 1, Failures: 0, Skips: 0
===============================================
===============================================
Default suite
Total tests run: 1, Failures: 0, Skips: 0
===============================================
[TestNG] Time taken by org.testng.reporters.jq.Main@4f8e5cde: 166 ms
[TestNG] Time taken by org.testng.reporters.XMLReporter@7e774085: 38 ms
[TestNG] Time taken by org.testng.reporters.EmailableReporter2@442d9b6e: 7 ms
[TestNG] Time taken by [FailedReporter passed=0 failed=0 skipped=0]: 1 ms
[TestNG] Time taken by org.testng.reporters.SuiteHTMLReporter@4e515669: 14 ms
[TestNG] Time taken by org.testng.reporters.JUnitReportReporter@368102c8: 2 ms
Executing iterative build steps
Seeking test results
Found 0 test results
Finished: SUCCESS
=======================================================================