CAP526 – Software Testing and Quality Assurance

Home Work – 2
Course code: cap 526 course name: software
testing

Programme name: M.c.a Programme code: 204

Section: D3803 roll-on: D43

Instructor: MISS GARGI SHARMA Student name: Saurabh

Sharma

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.

PROBLEMS OF WHITE BOX:

• Since tests can be very complex, highly skilled resources are required, with thorough
knowledge of programming and implementation.
• Test script maintenance can be a burden if the implementation changes too frequently.
• Since this method of testing it closely tied with the application being testing, tools to cater
to every kind of implementation/platform may not be readily available.
• White Box Testing is like the work of a mechanic who examines the engine to see why the
car is not moving.

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

Equivalence Types of input Test data Results

Value<5digit Character deep warning

+numeric

Value>5 Character + deepak valid

numeric

Value=capital Character DEEPAK warning

letters +numeric

Special Character Deep_123 valid

character but +numeric +
only underscore underscore

Q5. Explain the key elements involved in formal reviews?

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

Q6. Is it acceptable to release a Software Product that has Configuration Bugs?

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

2) MANUFACTURER: it is also important because when the hardware are under

development stage at that time developer fix some of the qualities like only text no graphics or
only A4 size sheets not any other type of sheet

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

Static white box testing Dynamic white box testing

• Peer Review Unit Testing Code Testing Code

Comlexity
• Formal • Integration • Function
Testing Testing
• Inspection
• System • Path
• Walkthrough Testing
• Statement
• User
Acceptance • condition

1) UNIT TESTING: In computer programming, unit testing is a software verification and

validation method in which a programmer tests if individual units of source code are fit for use. A
unit is the smallest testable part of an application. In procedural programming a unit may be an
individual function or procedure.

2) INTEGRATION TESTING : Integration testing is the phase in software testing in which

individual software modules are combined and tested as a group. It occurs after unit testing and
before system testing. Integration testing takes as its input modules that have been unit tested,
groups them in larger aggregates, applies tests defined in an integration test plan to those
aggregates, and delivers as its output the integrated system ready for system testing.

3) SYSTEM TESTING: System testing of software or hardware is testing conducted on a

complete, integrated system to evaluate the system's compliance with its specified requirements.
System testing falls within the scope of black box testing, and as such, should require no
knowledge of the inner design of the code or logic.

4) USER ACCEPTANCE TESTING: acceptance testing is black-box testing performed on a

system prior to its delivery. It is also known as functional testing, black-box testing, release
acceptance, QA testing, application testing, confidence testing, final testing, validation testing, or
factory acceptance testing.
In software development, acceptance testing by the system provider is often distinguished from
acceptance testing by the customer (the user or client) prior to accepting transfer of ownership.
In such environments, acceptance testing performed by the customer is known as user
acceptance testing (UAT). This is also known as end-user testing, site (acceptance) testing, or
field (acceptance) testing.

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.

Software quality control refers to specified functional requirements as well as non-functional

requirements such as supportability, performance and usability. It also refers to the ability for
software to perform well in unforeseeable scenarios and to keep a relatively low defect rate.

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?

1. Is the entire conditional path reachable?

ANS: 1) Control flow error

2. If the pointers are used, are they initialized properly?

1) Data reference error

3. Is there any part of code unreachable?

1) Data reference error

4. Has the use of similar looking operators (e.g. &,&& or =,== in C)checked ?
1) Comparison error