italics on todo
This commit is contained in:
parent
e0c3aff6a1
commit
d590371820
@ -22,17 +22,17 @@ have been tested and those that have not. Clearly understanding the
|
||||
degree to which the system has been tested helps to assess progress,
|
||||
assess risk, and focus ongoing testing efforts.
|
||||
|
||||
*TODO:
|
||||
*TODO:*
|
||||
|
||||
- Review the [target audience](Target-and-Benefits),
|
||||
- *Review the [target audience](Target-and-Benefits),
|
||||
[environmental requirements](SRS#environmental), and [possible
|
||||
deployments](Design-Architecturel#deployment) to understand the
|
||||
set of possible system configurations that could be tested.
|
||||
- Use a table or list to describe that set of possible configurations.
|
||||
Mark each possibility with Pending, N/A, or Waived.
|
||||
- Track each test run with an issue in the issue tracker or an item in
|
||||
the [test-runs](Test-Runs) document.
|
||||
- Periodically review the set of possible system configurations to
|
||||
set of possible system configurations that could be tested.*
|
||||
- *Use a table or list to describe that set of possible configurations.
|
||||
Mark each possibility with Pending, N/A, or Waived.*
|
||||
- *Track each test run with an issue in the issue tracker or an item in
|
||||
the [test-runs](Test-Runs) document.*
|
||||
- *Periodically review the set of possible system configurations to
|
||||
identify any additional needed test runs.*
|
||||
|
||||
### ::Test Runs by Operating System and Browser
|
||||
|
Loading…
Reference in New Issue
Block a user