Make chimera mode default for page load tests
Categories
(Testing :: Raptor, enhancement, P3)
Tracking
(Not tracked)
People
(Reporter: davehunt, Unassigned)
References
Details
(Keywords: good-first-bug, Whiteboard: [fxp])
Attachments
(1 file)
The recommended way to run page load tests is to pass the --chimera
command line option so that for each browser cycle we gather both cold and warm page loads. To improve the user experience we should make this the default behaviour. This will also make local test runs more suitable for comparison to tests running in CI.
This bug will see the removal of the --chimera
command line option, and when running page load tests we will default to the chimera mode. Note that we should error out if --chimera
is passed with a suitable message so that users quickly learn of the change and can correct their command line usage.
Reporter | ||
Comment 1•4 years ago
|
||
:sparky we could take this further by removing --cold
and --page-cycles
so that page load tests only run in chimera mode. This would increase the complexity of the patch, but could ultimately further improve the user experience. These could also be follow up bugs. What do you think?
Comment 2•4 years ago
|
||
This bug would also involve adding a --warm
flag.
I don't think we should remove the --cold
or --page-cycles
options just yet since they can be useful for our local testing as well. Another thing is that non-pageload test types make use of these concepts when they run - benchmarks use page-cycles for their iterations for instance. If we have to add a test in the near future (pre-MPT migration), some of this functionality might still be needed. So I'd rather hold off on doing those larger changes until we get to the MPT-migration.
Maybe, like you're saying, we could file a follow up bug for those and discuss it further there?
Reporter | ||
Updated•1 year ago
|
Updated•1 year ago
|
Comment 3•1 year ago
|
||
Can you mentor me on this? I would love to fix this issue
Comment 4•1 year ago
|
||
:jijnyasa, certainly! Let's work on this one after we finish bug 1834752. :)
Updated•1 year ago
|
Comment 5•1 year ago
|
||
Comment 6•1 year ago
|
||
This good-first-bug hasn't had any activity for 2 months, it is automatically unassigned.
For more information, please visit BugBot documentation.
Description
•