Open pdehaan opened 6 years ago
@pdehaan Should my team create the Test Plan as we did for other experiments or do you want to do that? We can start creating it if we have some documentation for the experiment from which we can extract the needed details.
@SoftVision-PaulOiegas Probably makes sense for your team to write the test plan (once we have some code to test), as I assume you'll be doing most of the testing+verifying.
Sure thing! Waiting on the documentation and code then. Thanks!
Dearest @SoftVision-PaulOiegas,
We have some code in the repo, and it looks like @Softvision-CristinaBadescu has been busy testing. Not sure if your team has enough to go on yet for a test plan, or if we're blocked by #8 (Adding a basic README.md with instructions). If you're waiting on specific documentation, we may want to file specific bugs for what's blocking us.
Hi @pdehaan
Yes, Cristina is actively testing what already landed but at a lower rate since we are swarmed for the moment with several other tasks. Right now we are still helping our old Engineering QA team while we also migrated to new tasks (shield studies especially) that we will be doing as the new Test Pilot QA team.
However, the first draft of the Test Plan for Tabs Split is already in review, but we could use a review form you if you can help us. Here it is.
We also have the Test Cases created but we haven't imported them yet into Test Rail. Will let you know when this will happen.
Once we have a functioning add-on to play with, we should write a QA testplan that we can use to verify releases.
Initially, I'd want to make sure that devtools and fullscreen and Activity Stream and stuff like Min-Vid/Lockbox all work as expected with a split viewport.