From d59037182006135c920d73708aa273d815d0a55b Mon Sep 17 00:00:00 2001 From: William Sandner Date: Fri, 24 Aug 2018 13:42:19 +0200 Subject: [PATCH] italics on todo --- Test-Run-Suite.md | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/Test-Run-Suite.md b/Test-Run-Suite.md index cc4feae..5965284 100644 --- a/Test-Run-Suite.md +++ b/Test-Run-Suite.md @@ -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