Confirmed users
487
edits
Rpappalardo (talk | contribs) (initial page) |
Rpappalardo (talk | contribs) (formatting) |
||
Line 76: | Line 76: | ||
= Test Execution = | = Test Execution = | ||
== Summary == | |||
Of the three tests available, <code>make megabench</code> will probably be the one you use most. | |||
<code>make test</code> is largely for a quick smoke test and <code>make bench</code> doesn't do anything you can't do with the other two. | |||
[[#toc]] | |||
== make megabench == | |||
'''In Terminal''' | |||
$ make megabench | |||
<pre> | |||
./venv/bin/loads-runner --config=./config/megabench.ini --user-id=bonzogonzo --server-url=https://loop.stage.mozaws.net:443 loadtest.TestLoop.test_all | |||
[2015-05-21 16:00:21,868][11285] Detached. run --attach to reattach | |||
</pre> | |||
''''Open the following URL in browser:'''' | |||
https://loads.mozilla.services.com | |||
* Login with credentials provided by Loop dev/QA team | |||
* You will see real-time output from your test run in your browser | |||
[[#toc]] | |||
== make test == | == make test == | ||
'''Description''' | |||
Running <code>$ make test</code> allows you to kick off a loadtest locally against a remote endpoint, but then receive test output locally. | Running <code>$ make test</code> allows you to kick off a loadtest locally against a remote endpoint, but then receive test output locally. | ||
Line 188: | Line 218: | ||
[[#toc]] | [[#toc]] | ||