This question is based on black-box software testing techniques. 1.A. Write a br

Question

This question is based on black-box software testing techniques.

1.A. Write a brief functional description for the function.

1.B. Generate functional test cases based on the functional description.

1.C. Identify and specify the equivalence partitions and generate equivalence partitioning test cases.

1.D. Generate boundary value analysis test cases.

1.E. Write an actual program to implement the average function in any programming language. Apply the boundary value analysis test cases you’ve suggested in D.

Explanation / Answer

1 .A.

Black-box software testing is the testing in which internal coding or designing or implementation of the application is not known by the tester. This is also called behavioral testing. These test mainly functional or non functional testing but it mainly do functional testing. Tester finds mainly errors in the black box testing is incorrect or missing functions , interface errors, errors in data structures or external database access and behavior or performance errors etc.

Levels of black box testing

Integration Testing : It occurs before validation  testing and after unit testing. Its requirement is is to verify functional, performance, and reliability requirements of the application .

System testing : At the end system testing is done by tester at developer site to specify that we are fullfilling the proper requirement of the user or client.

Acceptance testing : This testing is done by the user or client to cheak wheathe we are getting proper application or not.

1 . B .

Functional test cases :

In the test cases proper discription of the bug is defined.

1.C .   The equivalence partitions and generate equivalence partitioning test cases because in this level of testing is done and it is also a usefull technique. In this we divide the set of test then according to that we started testing. In equivalence-partitioning technique we need to test only one condition from each partition. This is because we are assuming that all the conditions in one partition will be treated in the same way by the software. If one condition in a partition works, we assume all of the conditions in that partition will work, and so there is little point in testing any of these others. Similarly, if one of the conditions in a partition does not work, then we assume that none of the conditions in that partition will work so again there is little point in testing any more in that partition.

1. D .

Boundary testing is the process of testing between extreme ends or boundaries between partitions of the input values.

So these extreme ends like Start- End, Lower- Upper, Maximum-Minimum, Just Inside-Just Outside values are called boundary values and the testing is called "boundary testing".The basic idea in boundary value testing is to select input variable values at their:

Boundary Analysis testing is used when practically it is impossible to test large pool of test cases individually.

This testing is used to reduce very large number of test cases to manageable form. Very clear guidelines on determining test cases without compromising on the effectiveness of testing. Appropriate for calculation-intensive applications with large number of variables/inputs.

id Discription discription of errors Environment likes window 8 , 10 , 7 etc Source like URL. Visual proof like screenshoot. Steps to produce Sevirity impact of bug in any particular software. priority priorities of bugs. Date in which date bug was locked Name of tester Actual result Expected result

Related Questions

Navigate

• Browse (All)
• Browse T
• Subjects

---

---

Integrity-first tutoring: explanations and feedback only — we do not complete graded work. Learn more.