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

Use for questions involving problems with automated tests. Relevant for designing test automation, debugging test automation, automation tooling questions, and questions about when it is appropriate to automate. Questions regarding specific tools should tag those tools as well.

0 votes
Accepted

Sanity vs smoke testing

In this case, "sanity test" and "smoke test" are interchangeable. Wikipedia acknowledges a relationship between these two terms as well (also on the "smoke testing (software)" page). Both terms refer …
Thomas Owens's user avatar
  • 1,601
0 votes
Accepted

Should I write redundant unit tests for property setters/getters?

If your policy is to write at least one automated unit test for every externally visible element of the application/system, then I would expect that you would have at least one automated unit test for …
Thomas Owens's user avatar
  • 1,601
3 votes
Accepted

Test Strategy Documentation for test automation

Usually, a test strategy is defined at the system or product level and includes a discussion of all levels and types of test. It would have a discussion of unit, integration and system-level tests, au …
Thomas Owens's user avatar
  • 1,601
1 vote

Should you write tests that are basically for no-op to catch errors? (e.g. test a transition...

If you were to apply equivalence partitioning, you would end up with a few partitions: x < 5 5 <= x <= 12 x > 12 Given that requirement, I would expect at least those three test cases to assert beha …
Thomas Owens's user avatar
  • 1,601
5 votes
Accepted

Is security testing the sole responsibility of testers or part of a mixed team?

All aspects of quality - functional and non-functional testing - should be solved by the whole team. Introducing a wall where developers develop and testers test introduces hand-offs, which increases …
Thomas Owens's user avatar
  • 1,601
2 votes
Accepted

Security test plan for vulnerability test

If you're interested in relevant standards, the most relevant one is likely to be IEEE Standard 1012, which is the IEEE Standard for System, Software, and Hardware Verification and Validation. I've no …
Thomas Owens's user avatar
  • 1,601
2 votes

Should you create a manual test script before automating it?

There's no one answer to this. It's highly dependent on the context in which you are working. For example, I've worked in fields with varying degrees of regulation, where traceability from requirement …
Thomas Owens's user avatar
  • 1,601
1 vote

What should be the testing type for a new version of an automated test case if edited manually

This is almost certainly going to depend on your team's or organization's process. Some teams and organizations that I have worked with require that new or modified test cases be executed manually bef …
Thomas Owens's user avatar
  • 1,601
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