Ch4 Flashcards
Is testing an easy task?
No, even for a simple program it will have a lot of test cases. Assume you want to test a program with 100k statements, you would need a lot of test cases an considerations.
We Have a program takes a number as input and classifies it as Positive, Negative, or Zero. What are test cases you can do?
1-test case for positive number (ex:when the input is positive does the program run?)
2-test case for negative number
3-test case for zero
4-test case for large positive number
5-test case for large negative number
6-test case for the not numeric input
7-test case for the decimal number
8-test case for empty input
9-test case if the program gives the right output (ex: when the input is positive does the program say that?
How many statements does a typical GYM and a payroll program have?
15k for GYM
and much more for the payroll
Why is software development prone (ميال) to errors?
Because it involves ambiguity, assumptions, and flawed human communication, which can lead to misunderstandings and mistakes.
What happens when changes are made to software?
Each change, whether adding new features or fixing defects, can introduce new errors or break existing functionality.
How to reduce the risk of errors whenever doing a change to our software?
by doing software testing
What is a common issue in software development requirements?
Ambiguity—different people understand the same requirement in different ways, leading to miscommunication.
How does ambiguity affect software projects?
it can cause misunderstandings, leading to incorrect implementations, rework, delays, and project failure.
What is testing?
Testing is the process of executing a program with intention of finding errors.
What is IEEE definition of testing
1-The process of operating a system or component under specified condition, observing or recording the results, and making an evaluation of some aspect of the system or component.
2-The process of analyzing a software item to detect the difference between the existing and required conditions ( that is, bugs ) and evaluate the features of the software item. (Meaning you run the item check how it performs, and how it should perform, and the difference is the bugs, you then evaluate how it did in order to fix it ).
What are SW testing objectives?
1-Direct objectives:
2-Indirect objectives
What are the direct objectives of software testing
1-To identify and reveal as many errors as possible in the tested SW.
2-To bring the tested SW, after correction of the identified errors and retesting, to an acceptable level of quality.
3-To perform the required tests efficiently and effectively, within the limits budgetary and scheduling limitation.
4-Reduce errors when doing a change to the software.
What are the indirect objectives of software testing
1- to make a record of SW errors found (by corrective and preventing actions) ,that will help with error prevention, since we already have and know the errors, we don’t do it again
Who Does Testing ?
1-Software Tester
2-Software Developer
3-Project Lead / Manager
4-End User
Depending on what someone does testing
It depends on the process and the associated stakeholders of the project(s)
Is technical knowledge important for the tester?
Yes, it helps the testing process to be more efficient and more effective and help the tester discover underlying erros.
Do we have a bug free software?
no, even with software testing, we can’t take it a a certification that it it 100% bug free.
Since software can’t be 100% bug free, how much errors should the software have?
1-as minimum as possible.
2-make sure that the bugs don’t affect the main functionality of the software
3-They are fine if they only have minor affects on the applications
When to Start Testing?
1-we try to start testing at early stages, to find errors earlier and reduce the cost and time of fixing them and deliver an error free software to the client.
2-Requirements Gathering phase and continued till the deployment.
When to Stop Testing?
1-It is difficult to determine when to stop testing
2-testing is a never-ending process and no one can claim that a software is 100% tested
What are some aspects to consider, when you want to stop testing?
1-Test Coverage is Sufficient (All critical test cases are executed and code coverage meets an acceptable threshold )
2-Defect Rate is Acceptable ((No critical bugs remain, and new defects are minimal does not affect the overall functionality of the software)
3-Time or Budget Limits are Reached (Testing must stop due to project deadlines or resource constraints)
4-Requirements Are Met and Approved (All functional and business needs are verified, and stakeholders approve the results)
What is code coverage?
Every statement of the code is covered by a test case
code coverage vs test coverage
code coverage (code fully tested)
test coverage (functionality and requirements are tested)
What are the levels of tetsing?
1-utit testing
2-integration
3-system testing
5-user acceptance testing
What is unit?
the smallest piece of code that can be isolated into a stand alone module module within the that can be tested
What is unit testing?
1-Unit testing is a way of testing the smallest piece of code (make sure they’re working properly) referred to as a unit that can be logically isolated in a system (can be a module).
2-called white box testing
3-done by developer
4-focused on the functional correctness of standalone modules.
5-micro level of testing
What are the benefits of unit testing?
1-reduce cost and time of testing since we do it early
2-eary finding of errors
3-improve the quality of your code
What is integration testing?
1-comes after unit testing
2-done by developer and tester
3-shows how units work together
4-Individual module (units) are combined and tested as a group, it’s one thing if units walk well on their own but how do they perform together when combined
what is the function of the developer in unit testing?
writing the integration tests for crucial parts, since they have written the codes of the units, they have good knowledge on how they work alone.
What are the benefits of integration testing?
1-helps you determine that and ensure your application runs efficiently (all individual modules together).
2-Identifies interface issues between modules
Why do we do integration testing alone, why unit testing before?
because you may have an error in your unit, so having that well cause an interface error, some having your units tested and correct will reduce time and جهد for integration testing.
