Search Results
| Search type | Search syntax |
|---|---|
| Tags | [tag] |
| Exact | "words here" |
| Author |
user:1234 user:me (yours) |
| Score |
score:3 (3+) score:0 (none) |
| Answers |
answers:3 (3+) answers:0 (none) isaccepted:yes hasaccepted:no inquestion:1234 |
| Views | views:250 |
| Code | code:"if (foo != bar)" |
| Sections |
title:apples body:"apples oranges" |
| URL | url:"*.example.com" |
| Saves | in:saves |
| Status |
closed:yes duplicate:no migrated:no wiki:no |
| Types |
is:question is:answer |
| Exclude |
-[tag] -apples |
| For more details on advanced search visit our help page | |
Results tagged with documentation
Search options not deleted
user 16597
Test documentation describes the artifacts created before, during, and after testing for the purpose of communicating with stakeholders to solicit feedback, to capture your intended approach to provide guidance for your team, to provide actionable information for business decision makers, and to record your findings for due diligence.
3
votes
2
answers
101
views
How do we effectively use mind maps (or anything similar) to demonstrate key areas (to test ...
While I was trying to communicate the business impact to my team I found it difficult to emphasize on it by the testing plan or documentation I prepared. …
- 917