(lilaram anjane)Software testing.pptx
-
Upload
anonymous-qecoczr -
Category
Documents
-
view
69 -
download
0
Transcript of (lilaram anjane)Software testing.pptx
![Page 1: (lilaram anjane)Software testing.pptx](https://reader031.fdocuments.net/reader031/viewer/2022033010/563dba40550346aa9aa40229/html5/thumbnails/1.jpg)
Software testing
Lilaram Anjane
Software Testing Introduction
![Page 2: (lilaram anjane)Software testing.pptx](https://reader031.fdocuments.net/reader031/viewer/2022033010/563dba40550346aa9aa40229/html5/thumbnails/2.jpg)
Introduction to software Testing When to start and stop Testing. Seven Principles of Testing. Software Development Life Cycle. (Waterfall model, Incremental Model, Prototype Model, Spiral Model,V model, Agile Model.)
Software testing Life cycle.
Contents:
![Page 3: (lilaram anjane)Software testing.pptx](https://reader031.fdocuments.net/reader031/viewer/2022033010/563dba40550346aa9aa40229/html5/thumbnails/3.jpg)
Software testing is an activity to check whether the actual result match the expected result and to ensure that software system is defect free.
Testing is process of evaluating a system or its components with intent to find that whether it satisfies requirements or not.
three important factors for software testing
1)Software should test within time period. 2)It should be cost effective. 3)It should be quality product.
Introduction to Software Testing
![Page 4: (lilaram anjane)Software testing.pptx](https://reader031.fdocuments.net/reader031/viewer/2022033010/563dba40550346aa9aa40229/html5/thumbnails/4.jpg)
Start of testing-1)As early as possible.2)At requirement gathering phase3)Depend of software development model.
Stop of testing-1)Completion of test case execution.2)Completion of Functional and code coverage to
certain point.3)Testing Deadlines.4)No high priority bugs are identified.5)Management decision.
When to start and stop testing
![Page 5: (lilaram anjane)Software testing.pptx](https://reader031.fdocuments.net/reader031/viewer/2022033010/563dba40550346aa9aa40229/html5/thumbnails/5.jpg)
P1 ->Testing shows Presence of defects. P2->Exhaustive testing is impossible. P3->Early Testing. P4->Defect Clustering. P5->Pesticide Paradox. P6->Testing is Context depending. P7->Absence of errors Fallacy.
Seven Principles of testing
![Page 6: (lilaram anjane)Software testing.pptx](https://reader031.fdocuments.net/reader031/viewer/2022033010/563dba40550346aa9aa40229/html5/thumbnails/6.jpg)
Software Development Life Cycle
![Page 7: (lilaram anjane)Software testing.pptx](https://reader031.fdocuments.net/reader031/viewer/2022033010/563dba40550346aa9aa40229/html5/thumbnails/7.jpg)
![Page 8: (lilaram anjane)Software testing.pptx](https://reader031.fdocuments.net/reader031/viewer/2022033010/563dba40550346aa9aa40229/html5/thumbnails/8.jpg)
1)Water Fall Model 2)Incremental model 3) Prototype Model 4)RAD Model 5)Spiral Model 6)V Model 7)Agile Model
Software Development Model.
![Page 9: (lilaram anjane)Software testing.pptx](https://reader031.fdocuments.net/reader031/viewer/2022033010/563dba40550346aa9aa40229/html5/thumbnails/9.jpg)
Water Fall Model
![Page 10: (lilaram anjane)Software testing.pptx](https://reader031.fdocuments.net/reader031/viewer/2022033010/563dba40550346aa9aa40229/html5/thumbnails/10.jpg)
![Page 11: (lilaram anjane)Software testing.pptx](https://reader031.fdocuments.net/reader031/viewer/2022033010/563dba40550346aa9aa40229/html5/thumbnails/11.jpg)
![Page 12: (lilaram anjane)Software testing.pptx](https://reader031.fdocuments.net/reader031/viewer/2022033010/563dba40550346aa9aa40229/html5/thumbnails/12.jpg)
Advantages of water fall model- Simple and easy understand and use.
Phases are processed and completed one at a time.
Works well for smaller projects where requirements are very well understood.
![Page 13: (lilaram anjane)Software testing.pptx](https://reader031.fdocuments.net/reader031/viewer/2022033010/563dba40550346aa9aa40229/html5/thumbnails/13.jpg)
Disadvantages of water fall model- It is very difficult to go back and change
something that was not well thought out in the concept stage.
No working software is produced until during the life cycle.
High amount of risk and uncertainty. Not a good model for complex and object
oriented projects. Poor model for long and ongoing project. Not suitable for the projects where requirements
are at a moderate to high risk of changing.
![Page 14: (lilaram anjane)Software testing.pptx](https://reader031.fdocuments.net/reader031/viewer/2022033010/563dba40550346aa9aa40229/html5/thumbnails/14.jpg)
Incremental Model
![Page 15: (lilaram anjane)Software testing.pptx](https://reader031.fdocuments.net/reader031/viewer/2022033010/563dba40550346aa9aa40229/html5/thumbnails/15.jpg)
![Page 16: (lilaram anjane)Software testing.pptx](https://reader031.fdocuments.net/reader031/viewer/2022033010/563dba40550346aa9aa40229/html5/thumbnails/16.jpg)
![Page 17: (lilaram anjane)Software testing.pptx](https://reader031.fdocuments.net/reader031/viewer/2022033010/563dba40550346aa9aa40229/html5/thumbnails/17.jpg)
1)Generates working s/w quickly and early during the software life cycle.
2)More flexible less costly to change scope and requirements.
3)Easier to test and debug during a smaller iterations.
4)Customer can respond to each built. 5)easier to manage risk because risky
pieces are identified and handled during it’s iteration.
Advantages Of Incremental Model
![Page 18: (lilaram anjane)Software testing.pptx](https://reader031.fdocuments.net/reader031/viewer/2022033010/563dba40550346aa9aa40229/html5/thumbnails/18.jpg)
1)Needs good planning and design.
2)Needs a clear and complete definition of the whole system before it can be broken down and built incrementally.
Disadvantages of Incremental model
![Page 19: (lilaram anjane)Software testing.pptx](https://reader031.fdocuments.net/reader031/viewer/2022033010/563dba40550346aa9aa40229/html5/thumbnails/19.jpg)
Prototype Model
![Page 20: (lilaram anjane)Software testing.pptx](https://reader031.fdocuments.net/reader031/viewer/2022033010/563dba40550346aa9aa40229/html5/thumbnails/20.jpg)
![Page 21: (lilaram anjane)Software testing.pptx](https://reader031.fdocuments.net/reader031/viewer/2022033010/563dba40550346aa9aa40229/html5/thumbnails/21.jpg)
Users are actively involved in the development
It provides a better system to users, as users have natural tendency to change their mind in specifying requirements and this method of developing systems supports this user tendency.
Errors can be detected much earlier as the system is mode side by side.
Quicker user feedback is available leading to better solutions.
Advantages of prototype model
![Page 22: (lilaram anjane)Software testing.pptx](https://reader031.fdocuments.net/reader031/viewer/2022033010/563dba40550346aa9aa40229/html5/thumbnails/22.jpg)
Leads to implementing and then repairing way of building systems.
Practically, this methodology may increase the complexity of the system as scope of the system may expand beyond original plans.
Disadvantage of prototype model
![Page 23: (lilaram anjane)Software testing.pptx](https://reader031.fdocuments.net/reader031/viewer/2022033010/563dba40550346aa9aa40229/html5/thumbnails/23.jpg)
RAD Model
![Page 24: (lilaram anjane)Software testing.pptx](https://reader031.fdocuments.net/reader031/viewer/2022033010/563dba40550346aa9aa40229/html5/thumbnails/24.jpg)
1)Reduced development time. 2)Increase reusability of components. 3)Quick initial reviews occur. 4)Encourages customer feedback. 5)Integration from very beginning solves a
lot of integration issues.
Advantages of the RAD Model
![Page 25: (lilaram anjane)Software testing.pptx](https://reader031.fdocuments.net/reader031/viewer/2022033010/563dba40550346aa9aa40229/html5/thumbnails/25.jpg)
Depends on strong team and individual performances for identifying business requirements.
Only system that can be modularized can be built using RAD.
Requires highly skilled developers/designers.
High dependency on modeling skills. Inapplicable to cheaper projects as cost of
modeling and automated code generation is very high.
Disadavantages of RAD model
![Page 26: (lilaram anjane)Software testing.pptx](https://reader031.fdocuments.net/reader031/viewer/2022033010/563dba40550346aa9aa40229/html5/thumbnails/26.jpg)
Spiral Model
![Page 27: (lilaram anjane)Software testing.pptx](https://reader031.fdocuments.net/reader031/viewer/2022033010/563dba40550346aa9aa40229/html5/thumbnails/27.jpg)
Cumulative cost Evaluate alternatives,Identify & resolve risks
Develop & verify next-level product
Plan next phase
Determine objectives,alternatives & constraints
Review & commitment
Prototypes
P1 P2 P3Operational PrototypeStart
End
Requirements plan
Development plan
Integration & Test plan
Requirements validation
Design, Validation & Verification
Detailed design
Coding
Unit & IntegrationTesting
Acceptance Testing
Concept Of Operation
![Page 28: (lilaram anjane)Software testing.pptx](https://reader031.fdocuments.net/reader031/viewer/2022033010/563dba40550346aa9aa40229/html5/thumbnails/28.jpg)
Spiral Model
![Page 29: (lilaram anjane)Software testing.pptx](https://reader031.fdocuments.net/reader031/viewer/2022033010/563dba40550346aa9aa40229/html5/thumbnails/29.jpg)
High amount of risk analysis hence, avoidance of risk is enhanced.
Good for large and mission-critical projects. Strong approval and documentation control. Additional functionality can be added at a
later date. Software is produced early in the software
life cycle.
Advantages of Spiral model
![Page 30: (lilaram anjane)Software testing.pptx](https://reader031.fdocuments.net/reader031/viewer/2022033010/563dba40550346aa9aa40229/html5/thumbnails/30.jpg)
Can be costly model to use Risk analysis requires highly specific
expertise. Project’s success is highly dependent on the
risk analysis phase. Does not work well for smaller projects.
Disadvantages of spiral model
![Page 31: (lilaram anjane)Software testing.pptx](https://reader031.fdocuments.net/reader031/viewer/2022033010/563dba40550346aa9aa40229/html5/thumbnails/31.jpg)
V Model
![Page 32: (lilaram anjane)Software testing.pptx](https://reader031.fdocuments.net/reader031/viewer/2022033010/563dba40550346aa9aa40229/html5/thumbnails/32.jpg)
Development and progress is very organized and systematic
Works well for smaller to medium sized projects.
Testing starts from beginning so ambiguities are identified from the beginning.
Easy to manage as each phase has well defined objectives and goals.
Advantages of V model
![Page 33: (lilaram anjane)Software testing.pptx](https://reader031.fdocuments.net/reader031/viewer/2022033010/563dba40550346aa9aa40229/html5/thumbnails/33.jpg)
Not suitable for bigger and complex projects Not suitable if the requirements are not
consistent. No working software is produced in the
intermediate stage. No provision for doing risk analysis so
uncertainty and risks are there.
disadvantages of V model
![Page 34: (lilaram anjane)Software testing.pptx](https://reader031.fdocuments.net/reader031/viewer/2022033010/563dba40550346aa9aa40229/html5/thumbnails/34.jpg)
Agile model
![Page 35: (lilaram anjane)Software testing.pptx](https://reader031.fdocuments.net/reader031/viewer/2022033010/563dba40550346aa9aa40229/html5/thumbnails/35.jpg)
![Page 36: (lilaram anjane)Software testing.pptx](https://reader031.fdocuments.net/reader031/viewer/2022033010/563dba40550346aa9aa40229/html5/thumbnails/36.jpg)
Customer satisfaction by rapid, Continuous delivery of useful s/w.
People and interactions are emphasized rather than process and tools, Customers developers and testers constantly interact with each other.
Working s/w is delivered frequently(Weeks rather than months).
Face to face communication is the best form of communication.
Close daily cooperation between business people and developers.
Advantages of Agile Model
![Page 37: (lilaram anjane)Software testing.pptx](https://reader031.fdocuments.net/reader031/viewer/2022033010/563dba40550346aa9aa40229/html5/thumbnails/37.jpg)
In case of some s/w deliverables, especially the large ones, it is diffcult to assess the effort required at the beginning of the s/w development life cycle.
There is lack of emphasis on necessary designing and documentation.
The project can easily get taken off track if the customer representative is not clear what final outcome that they want.
Disadvantages of Agile model
![Page 38: (lilaram anjane)Software testing.pptx](https://reader031.fdocuments.net/reader031/viewer/2022033010/563dba40550346aa9aa40229/html5/thumbnails/38.jpg)
Software Testing Life Cycle
![Page 39: (lilaram anjane)Software testing.pptx](https://reader031.fdocuments.net/reader031/viewer/2022033010/563dba40550346aa9aa40229/html5/thumbnails/39.jpg)
SDLC VS STLC
Requirement gathering
Requirement Analysis
DesignTest planning ,Test
design
Testing
Coding or development Test case writing
Testcase development
Deployment Final test execution
MaintenanceMaintenance
Testing
![Page 40: (lilaram anjane)Software testing.pptx](https://reader031.fdocuments.net/reader031/viewer/2022033010/563dba40550346aa9aa40229/html5/thumbnails/40.jpg)
Google.com
REFERENCES
![Page 41: (lilaram anjane)Software testing.pptx](https://reader031.fdocuments.net/reader031/viewer/2022033010/563dba40550346aa9aa40229/html5/thumbnails/41.jpg)
THANK YOU !!!