Chapter 3 Exercises


Q. 1
"Test Automation software is the best way to increase the effectiveness, efficiency and coverage of your software testing"(SmartBear, 2019).

Testerst automate tests in an automated testing tool because is able to playback pre-recorded and predefined actions, compare the results to the expected behavior and report the success or failure of these manual tests to a test engineer.
Automated tests differ from manual testing where a human being is responsible for single-handedly testing the functionality of the software in the way a user would. Because automated testing is done through an automation tool, less time is needed in exploratory tests and more time is needed in maintaining test scripts while increasing overall test coverage.

Q. 1.1
False sense of quality
Not reliable
Automation is not testing
Demands Maintenance Time and Effort
Slow feedback
Not many bugs found
Q. 2
Inheritance has resulted in some issues involved in testing of object-oriented software to be different from the testing issues of conventional software. In order to handle the testing issues of object-oriented software, conventional software testing tools have to be adapted or new tools need to be developed.
“To test a component you must be able to control its input and observe its output” (Binder, 2019).
Observability: refers to ease of determining if specified inputs affect the outputs; controllability refers to the ease of producing a specified output from a specified input.
Controllability: We define control condition as the condition that is difficult-to-test, as state of software required for its execution is difficult-to-create from user interface of software. The state that is difficult-to-create from user interface of software is defined as control state.
 Q. 3 & Q. 4
GitHub Team Repository

Q. 6
A) A test that does not reach the fault: Testing with n=0 or any other value that is not an integer.
B) A test that reaches the fault but does not infect: Testing with n<19.
C) A test that infects the star but does not propagate Any test that creates a faulty array (doesnt contain 19,29,etc.), where n>=19. But does not calls for iterator() nor toString().
D) A test that propagates but does not reveal A test where computePrimes(n) is called where n>=19 and iterator() is called with the resulting array, but toString() isn't.
E) A test that reveals the fault A test that calls every method.

Q.7
GitHub Team Repository


References:
SmartBear, 2019
Testingexcellence
A Testability Framework for Object- Oriented Software Testing

Comments

Post a Comment

Popular posts from this blog

Chapters 6.1 & 6.2

Image
Credits to @4vid Image Link 1. What two properties must be satisfied for an input domain to be properly partitioned?  Completeness: The partition must cover all of the domain. Disjoint: blocks should not overlap 2. What is an Input Domain Model (IDM)? Two Approaches to Input Domain Modeling: A. Interface-based approach. 􏰀 Develop characteristics directly from individual input parameters. 􏰀 Just use properties of the domains without considering the actual function under test. B. Functionality-based approach 􏰀 Develop characteristics from a behavioral view of the program under test. 􏰀 Use your understanding of what the system should do. 3. What gives more tests, each choice coverage or pair-wise coverage? Each Choice Coverage (ECC) states that one value from each block for each characteristic must be used in at least one test case. For example, for partitions [A, B] [1, 2] we can get [A, A], [B, B], [1, 1] and [2, 2] which are clearly redundant. Pair-
Read more

Final Exam Questions

1. Software fault: static error in the code. Software error: internal, not a normal behavior of the program due to a fault. Software failure: external, visible failure of the program. That it doesn't work basically. 2. Beizer discussed the goals of testing in terms of the “test process maturity levels” of an organization, where the levels are characterized by the testers’ goals. Level 0: Testing and debugging are the same. (Worst level) Level 1: Testing is only to find that your code doesn't work. Level 2: Get defensive or make an issue personal with testers because they broke your code. Level 3: Understand the job of a tester and take feedback as constructive criticism. Level 4: Become an expert software tester and make extreme good quality software. Work in harmony with testers. 3. Static Code Analysis is usually performed as part of a Code Review (also known as white-box testing). is a method of debugging by examining source code before a program is run . It’s done by ana
Read more

Course evaluation

Image
Credits to @rossf Image Link ECOA Evidence  I've been Ken Bauer's student for almost four years in several different courses, and his teaching method has always been a breath of fresh air. From flip learning to almost conventional teaching (since you grade your own exam) he's not afraid to make changes and give students the chance to explore self learning and to take responsibility on when and how they learn the content of the course. This is a skill that is very important acquire and that is needed on a daily basis in every job in the tech field. Personally i enjoyed the Software Quality and Testing course. There are many students that might not like this method of teaching applied on this course because it requires them to take responsibilities on their own learning and some students can't handle this type of control over their own learning. No negative feedback for this course, only that maybe some classes should be online.
Read more