...

...

...

...

...

The general recommendation for report formatting:[Do not include the section in reports ]

1. Make the page full-width Set your Confluence page to full-width to utilize the entire space available. This makes your report more readable and gives more room for arranging content aesthetically.

2. Image wide 1600px. This width offers a good balance, ensuring that images are clear and detailed without causing excessive loading times or appearing too large on the page.

3. For graphs from AWS CloudWatch use 1 minute metrics aggregation.

...

• What we are testing? Provide context of the test. Is it for a new service? Is it an experiment? Is it regression test?

  • Include major things like environment settings (ECS, non-ECS, Eureka, non-Eureka, w/RW split, etc…)

• What are the goals of the testing? Ex: Want to see the effect of using a different ec2 instance type. If regression: to see how vB compares to vA

  • Include defined SLAs, if available

• Reference the Jira(s)

]

Summary

[ A bulleted-list of the most important and relevant observations from the test results. What are the most important things the readers need to know about this testing effort? Some suggestions

...

The summary points should answer the goals stated in Overview: did the test achieve the goals laid out? What goals were not met and why? SLAs were met or not?

]

Recommendations & Jiras (Optional)

...

[ Include additional screenshots of graphs on the Cloudwatch and Grafana dashboards for completeness sake. Include any raw data that includes the timestamps of tests or any screenshots/charts/graphs. These data may be separate files or may be one Miror board or one Sheet/Doc that has everything in it. Raw data is important to consult for additional insights if the report omits them initially. ]

Test Artifacts

Attach the test artifacts - excluding any sensitive data. These artifacts are deviations from the main files that were checked into Github, but are relevant for this test.