342
edits
TestEngineering/Performance/RunningTests: Difference between revisions
TestEngineering/Performance/RunningTests (view source)
Revision as of 12:42, 7 May 2020
, 7 May 2020no edit summary
Alexandrui (talk | contribs) (Created page with "= Guide to running performance tests = == Prerequisites == === What? === To be able to run one or more performance tests you need to know which are those. The TestEngineeri...") |
Alexandrui (talk | contribs) No edit summary |
||
| Line 27: | Line 27: | ||
If you know exactly how the signature starts you can use a ^ in front of your search string and the results will narrow down to just that signature<br /> | If you know exactly how the signature starts you can use a ^ in front of your search string and the results will narrow down to just that signature<br /> | ||
[[File:Try fuzzy filter starts with.png|800 px|try fuzzy filter starts with]]<br /><br /> | [[File:Try fuzzy filter starts with.png|800 px|try fuzzy filter starts with]]<br /><br /> | ||
If you want to skip the chooser or the fuzzy and to push the test to try directly from the command line, you can use the option -q (from query). The option --no-push will allow you to check the jobs you’re pushing by printing them to the command line without actually pushing them to try. The option -m is pretty handy when you push several times the same test (and believe me, you will!).<br /> | |||
$ ./mach try fuzzy --full -q="'linux64 'raptor-tp6-1-firefox" -m="base for [bug/commit]" --no-push <br /> | |||
[[File:Try fuzzy filter platform test.png|800 px|try fuzzy filter platform test]] | |||