Q1) Black Box VS White Box Testing STQA Unit 3 Q5) Test case design Techniques- 1)Informal Review-

Q5) Test case design Techniques- 1)Informal Review- it is an informal static test technique perform on
Black Box- 1)Black box testing test functionality of system. 2)Request no knowledge of code. 3)It is any kind of requirements, design, code or project plan. During this, the work product is given to domain
usually done by tester or end users. 4)It checks input and output without looking at code. 5)To used- expert and feedback are reviewed by owner. This is applied many time during early stage of life cycle of
Selenium, I meter. 6)E.g. Functional testing, usability testing. White Box- 1)White box testing test the document. It takes place between two or three people. The goal is to keep the author and to improve
internal logic and structure of code. 2)It requires knowledge of code and programming. 3)It is usually quality of document. Informal review are not documented. 2)Walkthrough- it is a method of
done by developer. 4)It checks how the code works internally. 5)Tool used- Code analysers, Debuggers. conducting informal review. In this author, describe and explain work product in informal meeting to his
6)E.g. Unit testing, code review. Grey Box testing- 1)Combination of White Box and Black Box testing. peer or supervisor to get feedback. In this validity of purpose solution for work product is checked. It is
2)This method of testing is performed with less information about the internal structure of an cheaper to make changes when design is on paper. It is static method of quality assurance.
application. 3) Partial knowledge of internal structure. 4)Combines functional testing with limited 3)Inspections- It is defined as formal in depth group design to identify problem as close to their point of
structural insight. 5))Testers have some developer insights. origin as possible. It improve reliability, availability and maintainability of software product. Inspection
can be combined with structured systematic testing to provide powerful tool for creating defect free
Q2)Static Techniques. How static test case design techniques are useful for software testing
program. And inspection team consist of 3 to 8 member who plays role of moderator, author, reader,
It is software testing method to identify defects without actually executing the code. They focus on
recorder, and inspector.
reviewing and analysing documents, code and design at early stage of SDLC. Uses- They ensure early
detection through analysis of software artifacts without execution. 1)Reviews & Inspections: Catch Q6) Unit Testing & Integrated testing
ambiguities and missing requirements. 2)Static Code Analysis: Detect syntax errors, vulnerabilities, and 1)Unit testing- i)It is testing of individual component of product. ii)This testing is done by developer
ensure coding standards. 3)Checklists: Consistently cover common problem areas. 4)Data Flow itself. iii)Unit test cases are prepared before the test execution by the developer. iv)It is very important
Analysis: Identify data anomalies like uninitialized variables. 5)Control Flow Analysis: Validate logical to execute all unit test case as it helps to detect defect at early stage. v)If a defect occur on integrated
paths and detect unreachable code. 6)Model Reviews: Ensure design aligns with requirements. system, then it become difficult to find model because of which issue has occur. vi)Thus testing a
Three common static techniques- 1)Reviews. 2)Static Analysis Tools. 3)Model Validation. component individual is very important. vii)Stubs and drivers are basically used when one component
calls function from another component that is not developed, thus creating test environment for testing
Q3)Loop coverage testing & its types-Loop testing is kind of software testing that focuses exclusively on
of unit. viii)Tools- Automated testing frameworks. Example-Testing function or method within module.
correctness of construction. It is component of control structure testing. It is an example of white box
2)Integrated Testing- i)It is the testing when two or more models are integrated or merged to test if
testing and is used to test software loops. Types- 1)Simple loop- the loop has only one control structure
product works fine. ii)Once monitor and keyboard are ready, they should be integrated to verify if
( for, while or do-while) without nesting. Goal is to test the loop for maximum iterations. 2)Nested loop-
output is expected. iii)Tools- Both Automated & manual testing. iv)E.g. The computer has individual
Nested loop occur when one loop is inside another. Test Outer loop for its usual cases. Test inner loop
components as monitor, screen keyboard and mouse. Approaches in Integrated Testing- 1)Top-down
for its range of iterations. 3)Concatenated loop- This involves multiple loops that are not nested, but
approach- In this top level module developed and tested first. After that immediate sub model are
appear sequentially where one loop ends and another begins. 4)Unstructured loops- These loops do
integrated with popular model and tested. 2)Bottom-up approach- In this sub models are developed
not have clear entry & exit structured & are challenging to test as they can lead to unpredictable path.
and tested first, and then whole system is tested. 3)Mixed approach- Combination of top down &
Q4)Experienced based techniques- 1)Error Guessing. 2)Exploratory Testing. bottom up approach. Testing can start any time once model are developed. 4)Big bang approach- All
This technique use the tester experience to understand most important area of system that is area most modules are integrated into one go and are tested.
used by Customer and area that are most likely to fail. They tap into testers experience of defects found
Q7)Boundary value analysis & Equivalence class partition
in past when testing similar system. 1)Error Guessing- i)It is a simple technique that takes advantage of
1)Boundary Value analysis- i)In this technique, we focus on value at boundaries as it is found that many
tester intuition and experience to identify special tests that formal black box techniques could not
applications have high amount of issues on boundaries. ii)Boundary refers to value near the limit where
identify. ii)E.g. Pressing ESC key might have crashed similar application in past or pressing back button
the behaviour of system changes. iii)In this both valid and invalid inputs are being tested to verify the
or enter key on webpage. iii)This technique completely depends on testers experience, more the
issues. iv)It is a type of black box technique. v)E.g. If you want to test a field where value from 1 to 100
experience more error he can identify. iv)Another way of error guessing is creation of defects and
should be accepted, then we choose boundary value: 1-1, 1, 1+1, 100-1, 100, 100+1. Instead of using all
failure list. Common mistakes- Divided by zero. v)Handling null value in text field. File upload without
values we use 0, 1, 2, 99, 100, 101.
attachment. vi) Example: Testers might focus on complex calculations or frequently modified code
2)Equivalence Class Partition- i)In this input value to system are divided into different classes or groups
2)Exploratory Testing- i)This is used when specifications are either missing or in adequate and where
based on its similarity in outcome. ii)Hence, instead of using each and every input value, we can now
there is several time pressure. ii)It is an approach where tester explore the application without
use anyone value from group to test outcome. iii)This way we can maintain test coverage while
following a strict set of pre-written test cases. iii)Instead, they use their creativity, experience and
reducing amount of work & time spent. iv)E.g. Consider a ‘AGE’ text field that accepts only numbers
understanding of application to design and execute tests. iv)Goal is to discover unexpected issue or
from 18 to 60. There will 3 sets of classes or groups. Two invalid classes will be: i)Less than or equal to
bugs that might not be found using traditional test methods. v)It also allow tester to think like end-
17. ii)Greater than or equal to 61. A valid class will be anything between 18 & 60.
users, helping ensure application is user-friendly and robust. vi) Example: Tester navigates the software,
varying inputs to uncover unforeseen issues.
Q8)Explain- Statement, Branch, Path & Conditional coverage testing’s STQA Unit 3 Q11) Cookies testing – 1)It is form of software testing that examines cookies produced in your web
1)Statements Coverage Testing- i)It is one of widely used software testing, which comes under wide browser. 2)Cookie is a little piece of information that the web server stores in the text file on the users
box testing. ii)This technique is used to design white box test cases. iii)It involves execution of all hard dicks. 3)Each time the browser request page from the server, this information is transmitted back
statement in code at least once. iv)Used to calculate total number of executed statements in source to the server. 4)Cookies Testing ensures proper creation, storage & behaviour of cookies in a web app.
code out of total statement present In source code. v)Statement Coverage= No. of executed statement/ Key Checks- 1)Creation: Verify cookies are created after login. 2)Expiration: Check cookies expire as
Total no. of statement × 100. vi)Goal is to cover all possible executing statement and path line in code. expected. 3)Security: Test encryption and Secure flags. 4)Behaviour: Ensure proper app function when
vii)Advantage- Reveals unexecuted code segments. viii)Limitation: Does not ensure all logical conditions cookies are deleted, disabled, or corrupted. Example: i)Log in to a site → Verify session cookie is
have been exercised. 2)Branch Coverage Testing- i)It is used to cover all branches of control flow created. ii)Delete the cookie → Ensure the user is logged out.
graph. ii)It covers all possible outcomes ( True or false) of each condition of decision point at least once.
Q12)System Testing and Acceptance Testing
iii)This technique is a white box testing technique that ensures every branch of each decision point
1)System testing- i) A system as a whole i.e. completely developed system tested to find defects. ii)All
must be executed. iv)There are several methods to calculate branch coverage, but path finding is most
models are integrated to test as a complete system. iii)Scenarios prepared for system testing are run to
common method. v)In this method, number of parts of executed branches is used to calculate branch
find effects. iv)All model integrated and tested to verify that build product is as per customer
coverage. vi)Pros- Provides a more comprehensive assessment of code execution paths. viii)Cons-Does
requirement. v)End to end testing is performed to cover the complete scenario. vi) Focuses on
not guarantee coverage of all possible combinations of conditions.
validating the end-to-end functionality and behaviour. vii) Follows integration testing and precedes
3)Path Coverage Testing- i)It is a specific kind of methodical sequential testing in which each individual
acceptance testing. viii) Examples- End-to-end scenarios, performance testing, security testing.
line of code is assessed. ii)As a type of software testing path, cover testing is in category of technical
2)Acceptance testing- i)Once system testing is complete, product is ready to release to production
testing method. iii)It is labour-intensive and often reserved for specific vital section of code. iv)Way that
environment. ii)But before deployment, customers, acceptance and approval are required. iii)For this
path cover is testing works in that tester must look at each individual line of code that plays role in a
acceptance testing is done. iv) Gain user acceptance and ensure business needs are met.
module. v)For complete coverage, tester must look at each possible scenario so that all line of code are
Type of acceptance testing- i)Alpha testing- It is done internally by member of company who
covered. vi) Example: In a simple program with two conditional statements, path coverage ensures
developed the product. ii)Beta testing- It is done by actual users in product production environment.
testing both true and false branches of each condition 4)Conditional Coverage Testing- i) It is a type of
iii)User Acceptance testing- Testing is done at user and where the prepare UAT test cases are executed.
white box testing that tests all conditional expressions in program for all possible outcomes of
Q13)Regression Test & Importance- It is crucial in software development to ensure that new changes
condition. ii)It is also called predicate coverage testing. iii) In conditional coverage, all possible outcome
of all conditions must be tested at least once. iv) Examines the execution of logical conditions within the(such as updates, bug fixes, or feature additions) do not negatively affect the existing functionality of
code. v)Ensure that all possible outcomes of each condition are tested. vi)E.g. For "if-else" statement, the application. Importance- 1)Detecting New Bugs- It helps catch any unintended side effects or bugs
conditional coverage ensures testing both sides of the condition, including true and false evaluations. introduced by new code changes that might break previously working features. 2)Ensuring Stability-
Ensures that the system continues to function correctly after updates, maintaining its stability across
Q9) Performance Testing – It is done to verify system meets non-functional requirements identified in
different versions. 3)Validating Fixes- Confirms that previously reported issues have been fixed and that
SRS document. It verifies system behaves, and perform like response time throughout. Types of
the fixes do not cause new problems in other parts of the application. 4)Maintaining Software Quality-
performance testing- 1)Load testing- It is done to check how system response when load is increased
Helps ensure that the software retains its quality over time by verifying that new code does not disrupt
on system. Assess system behaviour under expected load E.g. If application response time is 30 sec with
the overall user experience. 5)Cost-Effective- By detecting bugs early in the testing phase, it prevents
number of logged in user as 1000, the testing is done by increasing number of users on site till Number
costly fixes after the software is released. 6)Confidence in Deployment- Reduces risks when deploying
reaches 1000. It verifies that response time is not increased as a load increase. 2)Stress testing- It is
new changes. 7)Improves User Experience- Prevents reoccurrence of old issues. 8)Supports
done beyond systems capacity to check at which point it fails. E.g. Taking the same example, testing is
Continuous Delivery- Ensures stability in agile and DevOps environments.
done by increasing number of user on site till Number reaches ( more than 1000) where in app
breakdown. Number of users is increased beyond capacity of product to handle it. Q14) Ad hoc testing- 1)It is an informal or unstructured software testing type that aims to break the
testing process in order to find possible defects or error at early possible stage. 2)It is done randomly
Non-Functional Testing focuses on evaluating the non-functional aspects of a software application, such
and it is usually an unplanned activity which does not follow any documentation and test to create test
as performance, security, usability, and scalability, rather than its core functionality.
cases. 3)Does not follow any structure way of testing and it is randomly done on any part of application.
Q10) Functional vs Non-functional testing. 1)Functional- i)It ensures that application works as 4)Main aim of this testing is to find defect by random checking. 5)This testing can be applied with a
expected. ii)It tests what the system does. iii)It is performed by tester familiar with business software testing technique called error guessing. Which required experience on system to guess the
requirement. iv)Tool used- Selenium, QTP. v)Common type or unit testing, integration testing. vi)E.g. most likely source of error. 6)Sometimes it is very difficult to reproduce the defects as there is no test
checking logic functionality, form submission . 2)Non-Functional- i) It ensures that application performs steps or requirements map to it. 7)Example- Testing an e-commerce site by entering random inputs in
well under various condition. ii)It tests how system perform. iii)It is performed by tester specialised in search boxes or clicking on links unpredictably to find errors.
performance, speed or reliability. iv)Tool used- I Meter, LoadRunner. v)Common type load testing,
security testing. vi)E.g. testing response time, system security.