search

dialex / start-testing

A crowdsourced testing course, written by testers for testers wannabes.
https://dialex.github.io/start-testing
Creative Commons Attribution 4.0 International
48 stars 7 forks source link

Test types #13

Closed dialex closed 1 year ago

dialex commented 6 years ago

Types

dialex commented 6 years ago

Rapid Software Testing definition:

“Testing is the process of evaluating a product by learning about it through exploration and experimentation, which includes: questioning, study, modeling, observation and inference, output checking, etc.”

http://www.satisfice.com/blog/archives/1509

dialex commented 6 years ago

It’s important to remember, as testers, that these boundaries are put into examples because they are core to what the business wants to deliver. They are not there as boundary value tests.

on BDD

http://www.mwtestconsultancy.co.uk/bdd-testing-part-2/

dialex commented 6 years ago

Even if I run the most simple and shallow of tests, if it reveals a bug, helps me come up with a new test idea, or reveals some information that is new or useful to me, then it’s a good test. This doesn’t mean that I can solely rely on simple or shallow tests. -- Mark W.

dialex commented 6 years ago
dialex commented 4 years ago

Accessibility (a11y):

dialex commented 4 years ago

Black box testing

This is a “box” that takes some input and gives you some output. You don’t know what’s going on inside. Because we don’t have a direct knowledge or control over what’s inside we can only try to interact with it and observe the behavior.

As we gather our observations, we also need some evaluation rule(s) to make a judgment – is there a potential problem? ORACLES

Note that a perception of a problem will be different for different people. Therefore testing, being a service, must not rely solely on the testers’ perception of the problem. QUALITY DEF

-- http://automation-beyond.com/2016/08/30/on-white-box-and-black-box-testing/ ✅

White box testing

We see the code. We can read it. We can infer what it’s supposed to do. We can mentally execute it and identify possible issues. The code is in a transparent “box”. Or a “glass” box. Which, eventually, to contrast it with Black Box testing, became a White Box testing term, albeit slightly misleading in this form.

-- http://automation-beyond.com/2016/08/30/on-white-box-and-black-box-testing/ ✅

Acceptance test

Acceptance Criteria are conditions which a software application should satisfy to be accepted by a user or customer. Often these can also be used to guide the testing for a testing team. If the acceptance criteria are met, then the story has passed. The thing is - acceptance criteria has its limitations.

-- https://nickytests.blogspot.com/2017/05/the-limitations-of-acceptance-criteria.html

QA and Business analysts should take the stories chosen during the planning meeting, and turn them into automated acceptance tests. Programmers use the acceptance tests as requirements. They read those tests to find out what their stories are really supposed to do.

-- https://sites.google.com/site/unclebobconsultingllc/tdd-with-acceptance-tests-and-unit-tests

In our world, we need to come up with ways to convey our intentions and ideas clearly so we are not misunderstood by our colleagues. In software development, acceptance criteria aid the development team in knowing the expectations for a certain feature.

Why?

Who?

These are normally written by the product owner and reviewed by a member of the development team to ensure that there are no technical constraints and/or inconsistencies from a development perspective. In my team, it is first written by the product owner, then reviewed by a developer for the technical constraints, and finally a QA specialist for their knowledge of how the new feature should interact with the current system.

How?

There are multiple ways to write acceptance criteria. Our team prefers the scenario-oriented format as the team gets a better understanding of the requirements compared to one sentence scenarios. Given/When/Then format

-- https://thelifeofoneman.com/how-to-write-acceptance-criteria

Pratice

Acceptance tests

User Story 1

Acceptance Criteria

Limitations

You are expecting someone to know in advance, before seeing the software, exactly how the software application should be. So if you are testing strictly against the Acceptance Criteria - you are in essence trusting that, that person (or group of people) who wrote the acceptance criteria knows everything about what is needed before the software is built.

dialex commented 3 years ago

download