Mind Map Gallery How to Report Your Work
- Page：01
无数据
- 140
- 2
- 1
How to Report Your Work
Work reports are typically used to explain your progress on a work project or provide your conclusions and recommendations regarding a workplace issue.
Edited at 2020-10-10 07:02:32
- Recommended to you
- Outline
Reporting
Reporting Considerations
reporter safety
what will they think if I made no progress?
client
who am I reporting to and how do I relate to them?
rules
what rules and traditions are there for reporting here?
significance of the report
how will my report influence events?
subject of the report
how do other reports affect mine?
other agents of reporting
how do other reports affect mine?
medium
how will my report be seen, heard, and touched?
precision and confidence levels
what distinctions make a difference?
Reporting Structure Styles
3 level test story
status of the product
what it does
how it failed
how it might fail
in what ways will it matter to your clients
testing
how you operated and observed it
how you recognized the problems
what you have and have not tested yet
what you won't test at all (unless the clients object)
value
the risks and costs of testing or not testing
what made testing harder or slower
how testable (or not) the product is
what you need and what you recommend
Rapid testing style
General
Testing heuristics
Risk Catalog
Project specific
Product coverage outline
Risk list
Test strategy reference
schedule
issues
bugs
status dashboard
rapid report example
Mike Kelly's MCOASTER
mission
coverage
obstacles
audience
status
techniques
environment
risk
Test results reporting
Observation
Risk
Implication
scenario testing
Mission
Testers
Setup
Activities
Oracle notes
Test results
Exploratory charters
SBTM method for exploratory charters
Past
what happened during the session?
Results
What was achieved?
Obstacles
What got in the way or slowed things down?
Outlook
What's next? What remains to be done?
Feelings
How does the tester feel about all this?
Informal charter format
Strategy ideas
prelude to exploratory testing
Test notes tend to be more valuable when they include the motivation for a given test, or other clues to the tester’s mindset. Try to express a charter in one to three sentences. The charter may suggest what should be tested, how it should be tested and what problems to look for.
motivation for tests
perceived risks for DecideRight
A risk list is another useful tool to help guide a test strategy. Therisk list can be as long or as short as you like; it can also be brokendown by product or coverage areas
Issues
Problems encountered that hampered testing
Bugs encountered, raised or yet to raise
Platform
Platforms used for testing the product
Process
Test areas/functions of the product explored
what we tested, why we tested it, and why we believethat our testing were good enough.
e.g. Functional analysis, Functional exploration
References to test data
Other interesting elements
Reporting Styles
dashboards for status of a project
Coverage matrices
Scribble a list of test ideas down the y-axis and list aspects of some test coverage model—product elements, quality criteria, platforms, test techniques—across the x-axis. As an experiment, create multiple sheets using the same tests, but with a different coverage model on each sheet, and observe how a single test can provide coverage in a number of different dimensions. For a given coverage model, denser coverage of the matrix suggests (but does not prove) deeper coverage of the particular set of ideas on that table.
quality criteria coverage matrix example
product element coverage matrix
Bug taxonomies
Annotated diagrams
Risk & Strategy based reporting
Create a table with 2 columns - risk, strategy
Describe the risk in the first column and propose the strategy in the second column
example
Taken from Michael Bolton's Rapid Software Testing notes