Chapter 1 Flashcards
what is Software testing
is a process used to identify the correctness, completeness and quality of developed computer software.
Testing is executing a program on a tiny sample of the input domain
t
what are the Two Important aspect of testing:
1 Dynamic technique
2 Optimistic approximation
Why is Testing Important ?
- Cost of bugs: 60 B/year US Economy
- On average: 1-5 bugs/KLOC
Causes of Software Defects
- Faulty requirements definition
- Time Pressure
- Complex Code
- Many System Interactions
- Coding errors
- Complexity of Infrastructure
- Changing technologies
- Non compliance with standards
what are the Roles of Testing in Software Development?
- Testing helps to reduce the risk of problems occurring during operation
- Testing contribute to the quality of the software system
- Testing may be required to meet contractual requirements, legal requirements, or industry specific standards
explain Testing and Quality
- Testing ensures that key functional and non functional requirements are met
Testing measures the quality of software in terms of …
- the number of defects found
- the tests run
- the system covered by the tests
Do you think testing increases the quality of the software ?
- Testing cannot directly enhance quality.
- Testing can give confidence in the quality of the software if it finds fewer or no defects
what is Quality Assurance(QA)
is a way of preventing mistakes or defects in manufactured products when delivering solutions or services
List tester roles?
Functional Tester
Automation Tester
Performance Tester
Mobile Tester
Pen Tester
… is responsible for checking if the product works based on business requirements
Functional Tester
… is responsible for writing script that automate testing rather than manual testing the functionality
Automation Tester
… is responsible for testing the product on different load and report the finding the developer
Performance Tester
… is responsible for testing the product on different mobile devices
Mobile Tester
… is responsible for exposing all security flaws(SQL Injection, Cross scripting, session hijacking …)
Pen Tester-
List the Testing Levels
- Unit Testing
- Integration Testing
- System Testing
- Acceptance Testing
- Validation Testing
- Regression Testing
- Alpha Testing
- Beta Testing
explain unit testing
- Testing individual components or units of a software application to ensure they function correctly in isolation.
what are some key concepts of unit testing
Algorithms and logic
Data structures(global and local) Interfaces
Independent paths
Boundary conditions
Error handling
explain Integration Testing:
Verifying that different units or modules of the software work together as expected when integrated.
why is integration testing needed?
- Ensures Modules function together without adverse effects.
- Ensures Combined sub-functions produce the desired major function.
- It catches errors that may magnify from acceptable imprecision.
- Detects interfacing and timing issues not found in unit testing.
- Identifies resource contention problems not spotted in unit testing.
explain Validation Testing:
Determines if the software meets all of the requirement defined in the SRS
explain Regression Testing:
Is performed to ensure that recent code changes have not adversely affected existing features or functionality.
Regression testing involves selectively repeating existing …
validation tests
explain differences between Alpha and Beta testing
Alpha Testing: Conducted internally by developers or a dedicated QA team before releasing the software to a limited audience.
Beta Testing: conducted by a select group of external users or customers to identify issues and provide feedback before the software is released to the general public.
explain Acceptance Testing:
Evaluating the system’s compliance with business requirements and determining whether it is ready for deployment.
… Similar to validation testing except that customers are present or directly involved.
Acceptance Testing
List the test types
Functional Testing
Non-Functional Testing
Structural Testing
Re-testing related to Changes
explain Functional testing
Involves evaluating what the system does, often described in documents like requirements specifications or functional specifications.
List the Types of functional testing
Security Testing
Interoperability Testing
what is Security Testing
Investigates the functions relating to detection of threats, such as viruses, from malicious outsiders
explain Interoperability Testing
Evaluates the capability of the software product to interact with one or more specified components or systems.
… is the testing of ”how” the system works
Non-Functional Testing
what tests are included under Non-functional testing?
Performance Testing
Load Testing
Stress Testing
Usability Testing
Maintainability Testing
Reliability Testing
Portability Testing
explain Stress Testing
How will the system perform under very tough circumstances, many users, many transactions, low memory,..etc
explain Load Testing
How will the system perform if we do a single transaction so many times
explain Structural Testing
It’s expressed as a percentage and indicates how much of the code has been exercised by the tests.
A higher test coverage % is preferred in Structural Testing
t
retesting is aka …
Confirmation testing
explain retesting
After a defect is detected and fixed, the software should be re-tested to confirm that the original defect has been successfully removed.
explain Regression testing
is the repeated testing of an already tested program, after modification, to discover defects introduced as a result of the changes
What kind of test types will be performed at the Unit Testing level?
Functional Testing: Test individual functions or methods of the classes, modules, or components used by your software.
Structural Testing: Also known as white-box testing, it’s used to test the internal structures or workings of an application, as opposed to its functionality (i.e., black-box testing).
Retesting related to changes: If a specific function or module of the application is changed, then retesting is performed to ensure the changes didn’t introduce new bugs.
What kind of test types will be performed at the Integration Testing Level:
Functional Testing: Test the interaction between different software modules. It’s typically done using stubs and drivers.
Non-functional Testing: Performance and reliability testing can be done at this level if the modules have performance or reliability requirements.
Retesting related to changes: If the interaction between modules is changed, then retesting is performed to ensure the changes didn’t introduce new bugs.
What kind of test types will be performed at the System Testing Level:
Functional Testing: Test the system as a whole. It’s typically done on a complete integrated system to evaluate the system’s compliance with its specified requirements.
Non-functional Testing: This includes performance testing, load testing, stress testing, usability testing, etc. These are usually done once functional testing is completed.
Structural Testing: At this level, it’s typically limited to coverage analysis.
Retesting related to changes: If there are major changes in the system requirements, then retesting is performed to ensure the changes didn’t introduce new bugs.
What kind of test types will be performed at the Validation Testing Level:
Functional Testing: Validation testing, also known as user acceptance testing (UAT), primarily focuses on functional testing from the perspective of end-users to ensure that the system meets their needs.
Non-functional Testing: It may involve some non-functional testing to validate user experience aspects such as usability.
Retesting: After changes are made based on user feedback or business requirements, retesting involves rerunning validation tests to ensure that the changes satisfy user needs.
What kind of test types will be performed at the Alpha and Beta Testing Level:
Functional Testing: Both alpha and beta testing primarily focus on functional testing, evaluating the software’s functionality in controlled or real-world environments.
Non-functional Testing: They may also involve non-functional testing to gather feedback on aspects such as performance and usability from end-users.
Retesting: After collecting feedback from alpha or beta testing, retesting involves addressing reported issues and ensuring that subsequent releases address identified concerns.
what are the techniques of testing:
1 Black box testing
2 White box testing
explain Black Box Testing
What it is: Testers check the software without knowing its internal code. They focus on inputs, outputs, and requirements.
How it works: Testers create tests based on what the software should do. They observe if the output matches the expected results.
Advantages: Easy for non-programmers to conduct. It emphasizes user experience and requirement compliance.
Give examples of BB Testing
- You input valid credentials (username and password) and check if it logs in successfully.
- You input invalid credentials and check if it displays an error message.
- You try logging in without entering any credentials and check if it prompts for required fields.
- `You verify if after successful login, it redirects to the user’s dashboard page.
what is Black Box Testing’s Limitation
It doesn’t reveal errors hidden in the implementation details
explain white box testing
What it is: Testers examine the internal code, design, and paths of the software.
How it works: Testers create tests based on the software’s internal structure, aiming to cover all code paths and conditions.
Advantages: Provides insights into code quality, finds errors not apparent in black box testing, and helps optimize code.
Give examples for WB testing
- Test to ensure correct authentication process.
- Test to verify session management, like session timeout.
- Test to check if password encryption is implemented properly.
- Test to ensure error handling for database connection failures.
what are the Seven Testing Principles
1 Testing shows presence of defects
2 Exhaustive testing is impossible
3 Early testing
4 Defect clustering
5 Pesticide paradox
6 Testing is context dependent
7 Absence of errors fallacy
what are the Stages of Testing
- Test Planning
- Analysis and Design
- Implementation and Execution
- Evaluating exit criteria and Reporting
- Test Closure activities
List Test Planning Activities
Defining the Scope of Project
Determine Test Approach
Defining Test Strategy
Determine Test Resources
Define Exit Criteria
List Activities in the Analysis and Design Stage.
- Analysis of Business requirements
- Designing Test Scenarios
- Creating Test Data
- Designing Testcases based on Scenarios
- Test Environment Setup
- Executing the Testcases in givenTimeline
- Prioritizing the Testcases
- Writing Automation scripts if necessary
- Defect Logging and Tracking
- Test Case Status Reporting
What is the Evaluating exit criteria and Reporting Stage used for?
- To check the test Status against the exit criteria specified in test planning.
- To assess if more test are needed or if the exit criteria specified should be changed.
- To write a test summary report for stakeholders.
- To finalize and archive testware such as scripts, test environments, etc. for later reuse.
- To handover the testware to the maintenance organization. They will give support to the software.
- To evaluate how the testing went and learn lessons for future releases and projects.
List the Testing Methodologies
Waterfall model
Iterative Model
Agile
What is the used of Verification and validation
To check during development if the product:
- Meets its specifications
- Delivers the functionality expected by the people paying for this product
… asks “Are we building the system right”
Verification
explain Verification
Is the process of evaluating whether a system or component meets the specified requirements and fulfills its intended purpose.
… answers “Are we building the right system?”
validation
explain validation
Evaluates a system during or at the end of the development process to determine whether it meets the specified requirements
explain the classical V model.
drawing in saved messages
explain the Defect lifecycle
