Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/perfana/test-events-loadrunner-cloud
https://github.com/perfana/test-events-loadrunner-cloud
Last synced: 2 days ago
JSON representation
- Host: GitHub
- URL: https://github.com/perfana/test-events-loadrunner-cloud
- Owner: perfana
- License: apache-2.0
- Created: 2020-11-03T14:55:39.000Z (about 4 years ago)
- Default Branch: main
- Last Pushed: 2024-04-06T12:41:21.000Z (9 months ago)
- Last Synced: 2024-11-09T04:15:20.563Z (about 2 months ago)
- Language: Java
- Size: 150 KB
- Stars: 0
- Watchers: 3
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# test-events-loadrunner-cloud
Events to start and stop for LoadRunner Cloud tests.
This event plugin start a LoadRunner Cloud test for the given LoadTest id.
## events
The `beforeTest` and `abortTest` event are implemented.
The `beforeTest` starts the load test and polls the LoadRunner Cloud server to see if
the test changes from `INITIALIZING` state to `RUNNING` state.
## messages
This is a `readyForStartParticipant`, so only when this event plugin sends a `Go!` message
on the `eventMessageBus` the event scheduler can progress to the `startTest` event.
When the LoadRunner Cloud test reaches the `RUNNING` state, the `Go!` message is sent.
## properties for LoadRunner Cloud:
* `loadRunnerUser` the user
* `loadRunnerPassword` the password
* `loadRunnerTenantId` the tenantId
* `loadRunnerProjectId` the projectId
* `loadRunnerLoadTestId` the loadTestId
* `loadRunnerUseTracingHeader` send tracing header via the run-time-settings (rts) (optional, default false)
* `pollingPeriodInSeconds` seconds between check if test is in RUNNING state (optional, default 10)
* `pollingMaxDurationInSeconds` max duration to check if test gets to RUNNING state (optional, default 300)
* `useProxy` activate proxy, for example to use with [mitmproxy](https://mitmproxy.org/)
* `proxyPort` port to use for proxy, uses localhost (optional, default 8888)
### notes
* tenantId: look up in browser url of LoadRunner Cloud: `TENANTID=X`
* projectId: look up in browser url of LoadRunner Cloud: `projectId=Y`
* loadTestId: look up in UI for defined test: LOAD TESTS > select test > look at `ID: Z` in Summary
## variables
The LoadRunner Cloud plugin sends the following variables with a message on the `EventMessageBus`:
* perfana-lrc-tenantId
* perfana-lrc-projectId
* perfana-lrc-runId
## tracing header
When `loadRunnerUseTracingHeader` is `true`, the tracing header is sent to the script run-time-settings.
The tracing header is the test run id.
In the scripts the tracing header can be injected as web header via `web_add_header` and `lr_get_attrib_string`:
web_add_header("perfana-test-run-id", lr_get_attrib_string("perfanaTestRunId"))
## use with events-*-maven-plugin
You can use the `test-events-loadrunner-cloud` as a plugin of the `events-*-maven-plugin`
by putting the `test-events-loadrunner-cloud` jar on the classpath of the plugin.
Use the `dependencies` element inside the `plugin` element as in the XML snippet below.
For example, with `perfana-test-client` plugin (from [example-pom.xml](src/test/resources/example-pom.xml)):
```xml
io.perfana
event-scheduler-maven-plugin
true
true
true
true
${systemUnderTest}
${version}
${workload}
${testEnvironment}
${testRunId}
${buildResultsUrl}
${rampupTimeInSeconds}
${constantLoadTimeInSeconds}
${annotations}
${tags}
LoadRunnerCloudEvent1
user
password
tenantId
1
2
true
PerfanaEvent1
http://localhost:8888
false
<_var1>my_value
io.perfana
test-events-loadrunner-cloud
${test-events-loadrunner-cloud.version}
io.perfana
perfana-java-client
${perfana-java-client.version}
```
Try this by calling:
mvn -f src/test/resources/example-pom.xml event-scheduler:test
## Todo
* create lookups for the project and test ids based on names
## References
Works with the Perfana event-scheduler framework:
* https://github.com/perfana/event-scheduler
* https://github.com/perfana/event-Scheduler-maven-plugin