Quality Testing

Quality is delighting customers

There is a registration form which contains three mandatory fields:

- User name (4 to 8 characters)

- Password

- Email ID

When applying Decision Table techniques, I would get 8 combinations.

Conditions

Rule 1

Rule 2

Rule 3

Rule 4

Rule 5

Rule 6

Rule 7

Rule 8

User name

T

T

T

T

F

F

F

F

Password

T

T

F

F

T

T

F

F

Email ID

T

F

T

F

T

F

T

F

I have following questions now.

1) Should I write separate test cases for User Name field using Equivalence Partition and Boundary Values techniques?

2) Should I include the EP/BV techniques with Decision Table itself?

Views: 220

Reply to This

Replies to This Discussion

Different techniques has different purposes. The decision table is good source to see what kind of possibilities there is and they are mostly testing the functionality. Then EP/BV has different purpose, and they can bring additional cases as well as some other (more technical things) can bring even more cases.

Let's handle only one field: Username - it has different kind of testing requirements. Length, possible special characters, different kind of character sets. E.g. can user name contain Finnish character like ö or ä. Or can it contain Arabic characters which are written from right to left. After that you might want to test some security related aspects also, and it adds more inputs to test. See e.g. http://testobsessed.com/wp-content/uploads/2011/04/testheuristicsch... that pdf for good hints. 

As you can see - it is very difficult to create full set of tests which are covering everything. That's why you have to reduce the test cases a lot and concentrate more to the exploratory testing where you don't write everything to test cases. 

Sorry - this didn't answer directly to your question. :D

software testing have different techniques.....static testing and dynamic testing are two important techniques related to software testing.
Black box And White Box testing are the another type of software testing .........
Black-Box Testing

The technique of analyzing without having any information of the interior technicalities of the program is called black-box analyzing. The specialist is unaware to the program structure and does not can get to the source code. Typically, while performing a black-box analyze, a specialist will interact with the body interface by providing information and analyzing results without knowing how and where the information is worked upon.
White-Box Testing

White-box tests the detailed research of inner reasoning and structure of the rule. White-box tests also called glass examining or open-box examining. In order to perform white-box examining on an application, a specialist needs to know the inner technicalities of the code.

The specialist needs to have a look inside the source code and find out which unit/chunk of the code is acting unnecessarily.

RSS

TTWT Magazine


Advertisement

Advertisement

Advertisement

Advertisement

© 2020   Created by Quality Testing.   Powered by

Badges  |  Report an Issue  |  Terms of Service