AWS prescriptive-guidance documentation change
Summary
Updated image path, changed stage headings to bold, fixed broken links, and improved sentence structure for clarity.
Security assessment
Changes involve formatting improvements, link updates, and minor text reordering without introducing security content. The mention of monitoring error rates is a standard performance testing practice, not a security-specific measure.
Diff
diff --git a/prescriptive-guidance/latest/performance-engineering-aws/test-automation.md b/prescriptive-guidance/latest/performance-engineering-aws/test-automation.md index abb3553c2..def096ce7 100644 --- a//prescriptive-guidance/latest/performance-engineering-aws/test-automation.md +++ b//prescriptive-guidance/latest/performance-engineering-aws/test-automation.md @@ -15 +15 @@ Use DevOps pipelines in the different stages for performance testing. - + @@ -19 +19 @@ The five stages for the test automation pipeline are: - 1. Set up – Use the test-data approaches described in the [Test-data generation](./test-data-generation.html) section for this stage. Generating realistic test data is critical to obtain valid test results. You must carefully create diverse test data that covers a wide range of use cases and closely matches live production data. Before running full-scale performance tests, you might need to run initial trial tests to validate the test scripts, environments, and monitoring tools. + 1. **Set up** ‒ Use the test-data approaches described in the Test-data generation section for this stage. Generating realistic test data is critical to obtain valid test results. You must carefully create diverse test data that covers a wide range of use cases and closely matches live production data. Before running full-scale performance tests, you might need to run initial trial tests to validate the test scripts, environments, and monitoring tools. @@ -21 +21 @@ The five stages for the test automation pipeline are: - 2. Test tool – To conduct the performance testing, select an appropriate load-testing tool, such as JMeter or ghz. Consider the best fit for your business needs in terms of simulating real-world user loads. + 2. **Test tool** ‒ To conduct the performance testing, select an appropriate load-testing tool, such as JMeter or ghz. Consider the best fit for your business needs in terms of simulating real-world user loads. @@ -23 +23 @@ The five stages for the test automation pipeline are: - 3. Test run – With the test tools and environments established, run end-to-end performance tests across a range of expected user loads and durations. Throughout the test, closely monitor the health of the system being tested. This is typically a long-running stage. Monitor error rates for automatic test invalidation, and stop the test if there are too many errors. + 3. **Test run** ‒ With the test tools and environments established, run end-to-end performance tests across a range of expected user loads and durations. Throughout the test, closely monitor the health of the system being tested. This is typically a long-running stage. Monitor error rates for automatic test invalidation, and stop the test if there are too many errors. @@ -27 +27 @@ The load-testing tool provides insights into resource utilization, response time - 4. Test reporting – Collect the test results along with application and test configuration. Automate collection of application configuration, test configuration, and results, which helps with recording the performance test–related data and storing it centrally. Maintaining performance data centrally helps with providing good insights and supports defining success criteria programmatically for your business. + 4. **Test reporting** ‒ Collect the test results along with application and test configuration. Automate collection of application configuration, test configuration, and results, which helps with recording the performance test–related data and storing it centrally. Maintaining performance data centrally helps with providing good insights and supports defining success criteria programmatically for your business. @@ -29 +29 @@ The load-testing tool provides insights into resource utilization, response time - 5. Clean up – After you complete a performance test run, reset the test environment and data to prepare for subsequent runs. First, you revert any changes made to the test data during the run. You must restore the databases and other data stores to their original state, reverting any new, updated, or deleted records generated during the test. + 5. **Clean up** ‒ After you complete a performance test run, reset the test environment and data to prepare for subsequent runs. First, you revert any changes made to the test data during the run. You must restore the databases and other data stores to their original state, reverting any new, updated, or deleted records generated during the test. @@ -38 +38 @@ Best practices include the following: - * Record the start and end time, and automatically generate URLs for logging, This helps you to filter observability data in that appropriate time window. monitoring, and tracing systems. + * Record the start and end time, and automatically generate URLs for logging, monitoring, and tracing systems. This helps you to filter observability data in that appropriate time window. @@ -59 +59 @@ Testing tools play an important part in any test automation. Popular choices for - * [ghz](https://ghz.sh/) is a command line utility and [Go](http://golang.org/) package for load testing and bench marking [gRPC](http://grpc.io) services. + * [ghz](https://ghz.sh/) is a command line utility and [Go](https://golang.org/) package for load testing and bench marking [gRPC](https://grpc.io) services.