Skip to main content
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
Search options not deleted user 684

A test strategy is the set of big-picture ideas embodying the overarching direction or design of a test effort.

5 votes

How to track which stories / functionality in an agile project have automation test coverage?

The first question to ask yourself is if this level of traceability is necessary. For some people, maybe the answer is yes. For others, perhaps not. If you don't need traceability between story and te …
Thomas Owens's user avatar
  • 1,601
1 vote

Should QA broadly speaking be aware of under the hood application flows, or should all testi...

This is a question of independence, specifically, the technical independence of the people performing testing from those designing and building the system. In my experience, this independence is most …
Thomas Owens's user avatar
  • 1,601
1 vote

Test Strategy Documents seem obsolete in agile teams. Am I wrong?

The idea of what is considered essential or wasteful work depends on the context. What is wasteful for one organization could be value-adding work for another, based on their needs and the needs of th …
Thomas Owens's user avatar
  • 1,601
3 votes

Difference between test strategy and test plan

The test strategy describes how - the overall test process, the techniques and practices used, design of test cases, selection of cases for retesting or regression, management and maintenance of the t …
Thomas Owens's user avatar
  • 1,601