Repository navigation
Flesh out test plan #240
Description
Activity
@c0mmander8 maybe you want to take this on?
- Clone the repo to your own account
- Edit your copy of the file (which can be done on GitHub)
- When you have a set of changes ready for review (not more often than once a day), submit a Pull Request
This would be very helpful and would benefit from your attention to detail.
Reacted by I3arana@c0mmander8 - here's an example of what I mean:
I'm slowly going through all the closed bugs and seeing what should be documented as tests to run before identifying a release. This could use additions - it's not complete! - and organization (e.g. consistent format, structure, etc).
This is much more valuable than release note edits!
@I3arana - maybe you could contribute here?
First task is to go back through old resolved bugs and describe the repro steps concisely here.
Eventually I'd like to get this edited into a checklist we could ask people to follow to verify correct behavior on various hardware and localization configurations.
Thats not a half.bad.idea
@c0mmander8 - I dug through the history and issues 1-206 predate the inclusion of the test plan document. It would be helpful for you to look through that range of issues, identify any that could benefit from a test description to prevent regressions, and suggest additions to the document here.
- locked and limited conversation to collaborators
on Nov 25, 2022
The list of tests to run in
res/notes/testplan.txtshould be fleshed out with the most of fixes and additions made so far. The doc should be something that we can have volunteers run through on a variety of hardware/emulator setups to make sure the eventual 1.2 release doesn't make anything worse.