CAP526 - Software Testing and Quality Assurance Home Work - 2
CAP526 - Software Testing and Quality Assurance Home Work - 2
CAP526 - Software Testing and Quality Assurance Home Work - 2
Home Work – 2
Course code: cap 526 course name: software
testing
I want to say that this assignment is my own individual work and this assignment is not copied
from any other student or from any source.
EVALUATOR MARKS: _____________________
SIGNATURE: ____________________________
Part – A
Q1. Why does knowing how the Software works influence how and what you should test?.
Ans:1 In white box testing the test cases is developed that covers all the parts of software. and
developer run or checked this test cases under different behavior. From this we know about the
working of software.
Q2. What is the biggest problem of White-Box Testing either Static or Dynamic?
Ans:2 DEFINITION:
White Box Testing (also known as Clear Box Testing, Open Box Testing, Glass Box Testing,
Transparent Box Testing or Structural Testing) is a software testing method in which the
internal structure/design/implementation of the item being tested is known to the tester. The
tester chooses inputs to exercise paths through the code and determines the appropriate
outputs. Programming know-how and the implementation knowledge is essential. White box
testing is testing beyond the user interface and into the nitty-gritty of a system.
Q3. How could you guarantee that your Software would never have a Configuration Problem?
ANS:3
• The developers implement software enhancements and report, analyze and fix defects.
• The software configuration manager is responsible for baselines identification
• The users may use the software configuration management system to retrieve a particular baseline, to
report defects or to propose software enhancements
• The testers report defects .
• NOTE: This is sort of a trick question. You'd need to ship the hardware and software together as one
package, the software would only work on that hardware, and the hardware would have to be completely
sealed, not having a single interface to the outside world.
Q4. Create the equivalence partitioning and write test cases to test the login screen containing
username and password?
ANS:4
ANS:5 formal reviews: In this technique the software is checked and if any
discrepancy is found ,remove it. There is only one team. The team members share the
code and check it. But in peer reviews we share our code with another team. the key
elements of formal reviews are:
1) Identify problem: This is a initial step, in this first we check the software and
identify the key problem.
2) Follow rules: then we make a some rules which we can follow for solve the
problem.
3) Prepare: apply the rules or apply techniques for solving the problem of software.
4) Write a report: last step is to write a report in detail about what we do and how
we do.
Part – B
ANS:6 yes, probably because we don’t know in which type of hardware the user run this
software. Your software may have a bug that appears under a broad class of configurations. For
example: if your software is works fine with laser printer but not with inkjet printer .it means
your software may have a bug specific only to a one particular configuration.
Q7. In addition to age and popularity what other criteria might you use to equivalence Partition
Hardware for Configuration testing?
ANS:7 1) TYPES: for equivalence partition hardware for configuration testing type is also checked
that is what type hardware is involved in the software. Because all the test case cannot be run on
all type of hardware. for example
If we use a simple text printing hardware like printer so for that we cannot test the cases which
are made for the fax machine as they both have different functionality and also do the serve
different purposes
Q8. What are the different levels of Testing and the goals of different levels? For each level Which
Testing Approach is more suitable?
ANS:8
Q9. Relate verification and validation to the Quality control and Quality Assurance with an
example?
ANS:9 Verification is a Quality control process that is used to evaluate whether or not a product,
service, or system complies with regulations, specifications, or conditions imposed at the start of
a development phase. Verification can be in development, scale-up, or production. This is often
an internal process.
Validation is Quality assurance process of establishing evidence that provides a high degree
of assurance that a product, service, or system accomplishes its intended requirements. This
often involves acceptance of fitness for purpose with end users and other product stakeholders.
Software Quality Control is the set of procedures used by organizations to ensure that a
software product will meet its quality goals at the best value to the customer, and to continually
improve the organization’s ability to produce software products in the future.
Q10. In a code review check list there are some items as given below .Categories them. Does the
code follow the coding conventions of the organization?
4. Has the use of similar looking operators (e.g. &,&& or =,== in C)checked ?
1) Comparison error