Scribd
Upload
23 views

Pract 4,19,12

Uploaded by

Janhavi More
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
23 views

Pract 4,19,12

Uploaded by

Janhavi More
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 5

Slip 4 Marks

Task 1 Design the test cases for railway reservation system


Task 2 1. Give any eight differences between quality assurance and
quality control.
2. Explain V-Model with labeled diagram.
V-model means verification and validation model. It is sequential path of execution of processes. Each phase
must be completed before the next phase begins. Under V-model, the corresponding testing phase of the

development phase is planned inparallel. So there is verification on one side of V & validation phase on the other

side of V.

Verification Phase:

1. Overall Business Requirement: In this first phase of the development cycle, the product requirements are

understood from customer perspective. This phase involves detailed communication with the customer to
understand his expectations and exact

requirements. The acceptance test design planning is done at this stage as business requirements can be used

as an input for acceptance testing.

2. Software Requirement: Once the product requirements are clearly known, the system can be designed. The

system design comprises of understanding & detailing the complete hardware, software & communication set up

for the product under

development. System test plan is designed based on system design. Doing this at earlier stage leaves more

time for actual test execution later.

3. High level design: High level specification are understood & designed in this phase. Usually more than one

technical approach is proposed & based on the technical & financial feasibility, the final decision is taken.

System design is broken down further into modules taking up different functionality.
4. Low level design: In this phase the detailed integral design for all the system modules is specified. It is

important that the design is compatible with the other modules in the system & other external system.
Components tests can be designed at

this stage based on the internal module design.

5. Coding: The actual coding of the system modules designed in the design phase is taken up in the coding

phase. The base suitable programming language is decided base on


Validation:

• Unit Testing: Unit testing designed in coding are executed on the code during this validation phase. This

helps to eliminate bugs at an early stage.

• Components testing: This is associated with module design helps to eliminate defects in individual
modules.

• Integration Testing: It is associated with high level design phase & it is performed to test the coexistence
& communication of the internal modules within the system

• System Testing: It is associated with system design phase. It checks the entire system functionality & the

communication of the system under development with external systems. Most of the software &

hardware compatibility issues can be uncovered using system test execution.

• Acceptance Testing: It is associated with overall & involves testing the product in user environment.

These tests uncover the compatibility issues with the other systems
available in the user environment. It also uncovers the non-functional issues such as load & performance defects
in the actual user

environment.

Slip 12 Marks
Task 1 Design the test cases for purchase order Management
Task 2 1.Enlist different techniques for finding defects and describe any
one technique with an example.
2.Enlist factors considered for selecting a testing tool for test
automation.
Different techniques for finding defects are:
1. Static technique

2. Dynamic technique

3. Operational technique

Dynamic Testing: Dynamic testing is a validation technique which includes dummy or actual execution of work

products to evaluate it with expected behavior. It includes black box testing methodology such as system testing
and unit testing. The testing methods evaluate the product with respect to requirements defined; designs created

and mark it as pass or fail.

1) Meeting requirements. 2) Technology expectations. 3) Training / skills. 4) Management aspects.


Slip 19 Marks
Task 1 Design the test cases for railway reservation system
Task 2 1.Draw defect prevention process cycle. State working of each
phase.
2. State any eight limitations of Manual Testing.

Defect Prevention -- Implementation of techniques, methodology and standard processes to


reduce the risk of defects.

Deliverable Baseline -- Establishment of milestones where deliverables will be considered


complete and ready for further development work. When a deliverable is baseline, any further

changes are controlled. Errors in a deliverable are not considered defects until after the

deliverable is baseline.

Defect Discovery -- Identification and reporting of defects for development team


acknowledgment. A defect is only termed discovered when it has been documented and

acknowledged as a valid defect by the development team member(s) responsible for the

component(s) in error.
Defect Resolution -- Work by the development team to prioritize, schedule and fix a defect,
and document the resolution. This also includes notification back to the tester to ensure that

the resolution is verified.

Process Improvement -- Identification and analysis of the process in which a defect


originated to identify ways to improve the process to prevent future occurrences of similar

defects. Also the validation process that should have identified the defect earlier is analyzed

to determine ways to strengthen that process.

Management Reporting -- Analysis and reporting of defect information to assist


management with risk management, process improvement and project management.

Limitations of Manual Testing:


• Manual Testing requires more time or more resources, sometimes both

• Performance testing is impractical in manual testing.

• Less Accuracy

• Executing same tests again and again time taking process as well as Tedious.

• GUI Objects Size difference and Color combinations etc.

Are not easy to find in Manual Testing.

• Not Suitable for Large scale projects and time bounded projects.
• Batch Testing is not possible, for each and every test execution Human user

Interaction is mandatory.
• Manual Test Case scope is very limited, if it is Automated test, scope is unlimited.

• Comparing large amount of data is impractical

• Checking relevance of search of operation is difficult

• Processing change requests during software maintenance takes more time.

You might also like