|Perfect Number of Pages to Order||5-10 Pages|
201 01 SF
a brief introduction
The goal of black-box testing is to check the output of the component under test. There are a variety of tactics to employ in order to test well. You will use equivalence partitioning in this exercise (EP). See Chapter 10 of the book and the slides in Canvas for more information.
Learning Objectives (1.1)
The activity is designed to help you understand the differences between black-box and white-box testing. The specific learning goal is to develop a thorough understanding of equivalence partitioning, a common black-box technique.
Getting ready (on paper)
Read the matrix program’s description, which is given below. (NOTE: For black-box testing, do not examine the source code!) At a unit test, specify test cases using equivalence partitioning (EP) approaches. To begin, create valid and incorrect equivalence classes. Then, for EP, specify test cases. Test inputs, execution circumstances, and expected outcome should all be specified. Ensure that both valid and invalid equivalence classes are covered by the test cases.
There is a single set of equivalence classes that covers both valid and invalid circumstances.
For EP, there are a number of test cases.
Case studies for BVA
Exercising (on computer)
Now use equivalence partitioning to test the matrix multiplication program (EP) Before the exercise, you should put the test cases you wrote down on paper into action. If you find equivalence classes you overlooked during the preparation, create new test cases. To finish this work, use the Python code.
Execute the test cases once they’ve been implemented.
It is necessary to write a test report that includes flaws. In your test report, carefully record your test outcomes. Remember to provide the test case ID, what is being tested, a description, the input, the expected outcome, and any other relevant details. Make a note of whether you passed or failed, as well as your thoughts on the problems you discovered.
EP has a complete set of test cases.
EP test and defect report
Application for conducting Black-box and White-box testing
The application’s goal is to use dynamic programming to imitate Chain Matrix Multiplication (CMM).
1- Execute the code that comes with this assignment.
2- The user interface will be generated by the application as shown below.
3- To add matrices, click the add button (number of columns in the first matrix must be equal to number of rows in the second matrix)
4- To compute the matrix multiplication, change the location of the parenthesis and click calculate.
Calculated time will determine how long it will take to perform the computation.
Using the position of the parenthesis around the matrices, determine the quickest computation time (ABCD..)
Conclusions and Analysis
For each test approach, consider the results of your testing. Think about the following issues:
Equivalence classes: How did equivalence classes come to be? Is it possible to make them better?
Test case selection: For each method, how many and what types of test cases did you choose?
Compare and contrast the testing methods:
Which technique performed best in this example (discovered the most problems, was the most cost-effective, etc.) and why?
When is each strategy most appropriate? Consider the situation in this case as well as in general.
When and why could different black-box test methodologies (at least 2) be appropriate?
Reflections and conclusions for each of the assignment 5 questions.
1. Provide an introduction for the section.
a. a summary of the report assignment, including its goal and purpose.
b. the White Box Testing Procedure, which should include a summary of your lab work.
2. It should provide a description of what you’re doing (same as for Black Box). Include McCabe’s Cyclomatic Complexity metric and the flow graph.
3. The Black Box Testing Procedure, which should include a summary and description of what you performed, i.e. the steps you took, so that others can replicate your technique. Include which test techniques were utilized, how they were implemented, and how the test cases for each approach were chosen.
a. Defects that have been discovered. Report on the number and types of problems discovered, as well as the coverage type).
a. White-Box vs. Black-Box Testing Compare and contrast white-box and black-box testing methods. Discuss the benefits and drawbacks of each strategy, as well as when to use them (situations, cases etc.) The number of pathways in a program can be determined using the white-box technique by analyzing the codes.
Choose which ones to put to the test. Using the following methods to reduce coverage:
Paths of logic
Paths on their own
Coverage of branches
Coverage of the statement
Software Testing and Quality Assurance, John Wiley & Sons, 2008.  Kshirasagar N. and Tripathy P., Software Testing and Quality Assurance, John Wiley & Sons, 2008.