Basics of Software Testing
Download as PPT, PDF2 likes1,071 views
The document discusses key concepts in software testing and quality analysis from the viewpoint of customers and producers. It defines bugs and errors, and outlines common causes like complexity, changing requirements, and time pressure. Testing aims to discover faults and weaknesses through execution with the intent of finding errors. The document also mentions software development lifecycles like waterfall model and V-model, as well as standards organizations. It stresses finding and fixing defects early to improve quality.
Basics of Software Testing
- 2. Basic concepts of Software Testing & Quality Analysis
- 3. Customers viewpoint Fit for use or other customer needs Producers viewpoint Meeting requirements
- 4. Delivered on time Within budget Meets requirement/expectation Maintainable Bug free
- 5. Bug/Issue is defined as a flaw in a system or system component that causes system or system component to fail to perform its required function.
- 6. Mistake Fault Failure/Crash Error
- 7. Miscommunication or No communication Software complexity Programming errors Changing requirements Time pressure Egos Poorly documented code Software development tools
- 9. Definitions Testing is process of trying to discover every conceivable fault or weakness in a work product. Testing is a process of executing a program with the intent of finding an error. A good test is that has a high probability of finding an as yet undiscovered error A successful test is that uncovers an as yet undiscovered error.
- 10. Waterfall Model Software Development Life Cycle Spiral Model
- 11. V V Model
- 12. Capability Maturity Model Integration Initial Repeatable Defined/Standard Managed/Measured Optimizing
- 13. ISO ( International Organization for Standardization ) SEI ( Software Engineering Institute ) IEEE ( Institute of Electrical & Electronics Engineers ) ANSI ( American National Standards Institute) Six Sigma
- 14. Severe bugs Critical softwares Hospital Bank Credit cards
- 15. Distribution of Bug detection
- 16. The cost of quality is free
- 17. Find defects. Find them as early as possible. Make sure that they get fixed.
- 18. Hunt for defects. Creatively destructive. Pursue Errors not people. Tester add value
- 19. Process of testing…… For the best future of work product Bugs are always celebrated
- 20. A lot of hidden efforts goes into a software product
- 21. We break software because we care
- 22. We don’t make softwares ; We make softwares better.
Editor's Notes
- #2: Welcome and thank you for joining us for the [21 CFR Part 11 for the plastics industry] Webinar. My name is Serge Jonnaert. I am Executive Vice President of Marketing at American MSI Corporation
- #5: What you should be looking for in a solution: * Centralized user rights management. Essentially access to any and all workstations or control panels is governed by a single database. * Database alteration alerts. Any attempt to tamper with the data should be recorded using triggers. * Auto secure time-outs. When a workstation or control panel is left unattended it should automatically slip into a secure mode. Record validation through hash algorithms. The FDA demands that you assure that the system is not fed with forged data.