1 / 28

TESTING

TESTING. Team 8: Nguyễn Hoàng Khánh Dương Quốc Việt Trang Thế Vinh. Introduce. Define: Testing Software Testing. Introduce. Define: Testing: IEEE Standard 610.12-1990

melody
Download Presentation

TESTING

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. TESTING Team 8: NguyễnHoàngKhánh DươngQuốcViệt TrangThếVinh

  2. Introduce • Define: • Testing • Software Testing

  3. Introduce • Define: • Testing: • IEEE Standard 610.12-1990 • Testing is the process of operating a system or component under specified conditions, observing or recording the results, and making an evaluation of some aspect of the system or component 

  4. Introduce • Define: • Testing: • Systematic Software TestingRick Craig and Stefan Jaskiel • Testing is a concurrent lifecycle process of engineering, using and maintaining testware in order to measure and improve the quality of the software being tested

  5. Introduce • Define: • Software Testing:

  6. Introduce • Define: • Software Testing: • An investigation conducted to provide stakeholders with information about the quality of the product or service under test.

  7. Introduce • Define: • Software Testing: • Provides an objective, independent view of the software to allow the business to appreciate and understand the risks at implementation of the software.

  8. Introduce • Define: • Software Testing: • Test techniques include, but are not limited to, the process of executing a program or application with the intent of finding software bugs .

  9. Introduce • Define: • Software Testing: • Software testing can also be stated as the process of validating and verifying that a software program/application/product: • Meets the business and technical requirements that guided its design and development. • Works as expected • Can be implemented with the same characteristics

  10. Introduce • Define: • Software Testing: • Software testing, depending on the testing method employed, can be implemented at any time in the development process.

  11. Introduce • Define: • Software Testing: • Testing can never completely identify all the defects within software

  12. Introduce • Define: • Software Testing: • Every software product has a target audience. For example, the audience for video game software is completely different from banking software. Therefore, when an organization develops or otherwise invests in a software product, it can assess whether the software product will be acceptable to its end users, its target audience, its purchasers, and other stakeholders. Software testing is the process of attempting to make this assessment.

  13. Introduce • Define: • Software Testing: • A study conducted by NIST (The National Institute of Standards and Technology) in 2002 reports that software bugs cost the US economy $59.5 billion annually. More than a third of this cost could be avoided if better software testing was performed.

  14. Software testing topics • Scope • Functional and non-functional testing • Defects and failures • Finding faults early • Compatibility • Static vs. dynamic testing • Software verification and validation • The software testing team • Software quality assurance (SQA)

  15. Software testing topics • Scope: • A primary purpose for testing is to detect software failures so that defects may be uncovered and corrected.

  16. Software testing topics • Functional and non-functional testing • Functional testing refers to tests that verify a specific action or function of the code. • Non-functional testing refers to aspects of the software that may not be related to a specific function or user action, such as scalability or security.

  17. Software testing topics • Defects and failures • Not all software defects are caused by coding errors. • One common source of expensive defects is caused by requirement. • A common source of requirements gaps is non-functional requirements such as scalability, maintainability, usability, performance and security

  18. Software testing topics • Finding faults early • It is commonly believed that the earlier a defect is found the cheaper it is to fix it. • For example, if a problem in the requirements is found only post-release, then it would cost 10–100 times more to fix than if it had already been found by the requirements review.

  19. Software testing topics • Compatibility • A common cause of software failure is a lack of compatibility with other application software, operating systems or target environments that differ greatly from the original (such as a terminal or GUI application intended to be run on the desktop now being required to become a web application, which must render in a web browser ).

  20. Software testing topics • Static vs. dynamic testing • There are many approaches to software testing. • Reviews, walkthroughs, or inspections are considered as static testing. • Executing programmed code with a given set of test cases is referred to as dynamic testing.

  21. Software testing topics • Software verification and validation • Verification is the process of evaluating a system or component to determine whether the products of a given development phase satisfy the conditions imposed at the start of that phase. • Validation is the process of evaluating a system or component during or at the end of the development process to determine whether it satisfies specified requirements.

  22. Software testing topics • The software testing team • Software testing can be done by software testers . • Regarding the periods and the different goals in software testing, different roles have been established: manager, test lead, test designer, tester, automation developer and test administrator.

  23. Software testing topics • Software quality assurance (SQA) • Software testing can be done by software testers . • Regarding the periods and the different goals in software testing, different roles have been established: manager, test lead, test designer, tester, automation developer and test administrator.

  24. Testing process The testing cycle Requirements analysis Test planning Test development Test execution Test reporting Test result analysis Defect Retesting Regression testing Test Closure

  25. Automated testing • What is "Automated Testing"? • Cost-Effective Automated Testing • Viable Automated Testing Methodologies • Managing Resistance to Change • Staffing Requirements • Summary • Introduction • Testing tools • Measurement in software testing

  26. Testing artifacts Software testing process can produce several artifacts Test plan  Traceability matrix  Test case Test script  Test suite Test data Test harness 

  27. Certifications • Software testing certification types • Exam-based • Education-based • Testing certifications • Certified Associate in Software Testing (CAST) • CATe offered by the International Institute for Software Testing • Certified Manager in Software Testing • Quality assurance certifications • CMSQ offered by the Quality Assurance Institute • CSQA offered by the Quality Assurance Institute

  28. Thank You ! www.themegallery.com

More Related