218
edits
Compatibility/System Addon/Automated Testing: Difference between revisions
Compatibility/System Addon/Automated Testing (view source)
Revision as of 13:14, 28 May 2025
, 28 May+category
Twisniewski (talk | contribs) (initial document) |
(+category) |
||
| (4 intermediate revisions by one other user not shown) | |||
| Line 22: | Line 22: | ||
== Tests requiring Linux == | == Tests requiring Linux == | ||
<syntaxhighlight lang="bash"> | |||
# samsung_com.py | |||
./mach test-interventions --headless --bug=1799968 | |||
</syntaxhighlight> | |||
== Tests requiring Windows or MacOS == | |||
<syntaxhighlight lang="bash"> | <syntaxhighlight lang="bash"> | ||
# saxoinvestor.fr | # saxoinvestor.fr | ||
./mach test-interventions --headless --bug=1719859 | ./mach test-interventions --headless --bug=1719859 | ||
</syntaxhighlight> | </syntaxhighlight> | ||
| Line 63: | Line 68: | ||
<syntaxhighlight lang="bash"> | <syntaxhighlight lang="bash"> | ||
# missingmail.usps.com | # missingmail.usps.com | ||
# note this test can take several minutes to run, as the site is very slow | |||
./mach test-interventions --headless --bug=1644830 --config=logins.json | ./mach test-interventions --headless --bug=1644830 --config=logins.json | ||
| Line 68: | Line 74: | ||
# note that Steam requires two-factor authentication, so you will be asked | # note that Steam requires two-factor authentication, so you will be asked | ||
# to provide a code twice by the test as it runs. | # to provide a code twice by the test as it runs. | ||
./mach test-interventions --headless --bug=1570108 --config=logins.json | ./mach test-interventions --headless --bug=1570108 --do2fa --config=logins.json | ||
</syntaxhighlight> | </syntaxhighlight> | ||
== logins.json file == | === Example logins.json file === | ||
The logins.json looks like this, only with actual passwords: | The logins.json looks like this, only with actual passwords: | ||
| Line 105: | Line 111: | ||
''FAILED'' tests require need to be checked to confirm whether the intervention is still working or necessary. Sometimes a test will fail because a site has changed, but it may fail simply due to a networking or other hiccup. As such it may be worth running each failing bug number's tests a second or third time, using the ''--bug='' parameter as shown above (including the config file if the test | ''FAILED'' tests require need to be checked to confirm whether the intervention is still working or necessary. Sometimes a test will fail because a site has changed, but it may fail simply due to a networking or other hiccup. As such it may be worth running each failing bug number's tests a second or third time, using the ''--bug='' parameter as shown above (including the config file if the test | ||
requires a login). | requires a login). | ||
[[Category:Web Compatibility]] | |||