Use JPT to test jira performance
https://github.com/atlassian/jira-performance-tests/blob/master/docs/tests/ON_PREMISE.md
When set jira URI to:
jira-performance-tests/examples/btf-test/src/test/java/com/atlassian/performance/tools/btftest/MyJiraOnPremiseIT.java
final URI myJira = new URI("http://192.168.1.1:8080"); // Official example is http://localhost:8090/jira/
jiraOnPremiseTest.setAdminLogin("admin");
jiraOnPremiseTest.setAdminPassword("admin");
Under jira-performance-tests/examples/btf-test run:
./mvnw verify
Got these errors:
[INFO]
[INFO] Results:
[INFO]
[ERROR] Errors:
[ERROR] MyJiraOnPremiseIT.testMyJira:55 ? Failed to run with [--jira-address, http://...
[INFO]
[ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0
[INFO]
[INFO]
[INFO] --- maven-failsafe-plugin:2.22.0:verify (default) @ btf-test ---
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 5.500 s
[INFO] Finished at: 2019-12-04T06:39:56Z
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-failsafe-plugin:2.22.0:verify (default) on project btf-test: There are test failures.
[ERROR]
[ERROR] Please refer to /home/vagrant/jira-performance-tests/examples/btf-test/target/failsafe-reports for the individual test results.
[ERROR] Please refer to dump files (if any exist) [date]-jvmRun[N].dump, [date].dumpstream and [date]-jvmRun[N].dumpstream.
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
My JIRA address is `http://192.168.1.1:8080`. It can been accessed. Why JPT can't recognize it?
This JPT repo hasn't been updated for more than 1 year. Does its source outdated?
If don't use this method. Other way also seems complex.
I had an issue with the version of chromedriver that I was using resulting in a similar error. After updating this, I was able to run the tool without any issue.
1. Have latest Chrome version installed
2. Install the latest chromedriver for your OS, unzip it and add the executable to your path (I am using a Mac) In my .bash_profile I added the following two lines:
- PATH="/Users/user/folder-with-chromedriver:${PATH}"
- export PATH
3. Run ./mvnw verify. Optionally with the -e or -X option for additional debugging information if above does not work.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.