Karteikarten
Flash Cards: Testing Levels & Types
Karten in diesem Stapel (26)
- 1BLACK BOX TESTINGtesting front end of software / app (buttons, links etc)
- 2WHITE BOX TESTINGtesting back end of soft (code)
- 3GREY BOX TESTING:testing both front & back and anywhere in between
- 4Unit TestingIndividual Component test performed by Developer
- 5Integration TestingComponents intergrated in groups tested QA Team
- 6System TestingWhole integrated system is tested QA Team
- 7Acceptance TestingAd-hoc testing to determine if it is ready for delivery, done by: UAT Team
- 8Functional TestingSoftware is tested by providing it with some related input so that the output can be evaluated against the requirements
- 9Non-Functional testingcheck non-functional aspects of a sofware application (performance, usability, reliability, etc)
- 10Smoke testingPerformed to make sure that application / software is stable before proceeding with further testing
Smoke testing is also known as build verification testing - 11Sanity testingExploratory testing where the QA engineer verifies all the menus, functions, commands available in the product and project are working fine.
Checking software for stability - 12Positive testingAny test done by the valid data is called positive testing
- 13Negative TestingAny test performed with invalid data is called negative testing
- 14Backend TestingTesting database & logs via SQL & Unix
Back-end testing involves data validation, table validation, column verification, logs, timestamps and flow - 15SQLStructured Query Language
- 16UNIX (UNICS)Uniplexed Operating and Computing System
- 17Regression TestingWhenever the reported bugs are fixed and when the new functionalities are tested
last testing before signing off the testing cycle - 18End to end TestingTesters test the software from start to finish under real-world scenarios like communication of the application with hardware, network, database and other applications.
- 19Transaction TestingTo perform this testing we have to make sure that the inserted data into the front-end, has been trasected to the database properly.
- 20Security testingTo determine how well is the system protected against unauthorized internal or external access
Done by specials Cybersecurity Team or Ethical Hackers - 21Cross-Browser / Cross - OS testingCompatibility Testing helps to determine how the software will work on different operational system or browsers.
- 22Load TestingLoad testing is an application under heavy loads, such as a website under a range of loads to determine at what point the system response time degrades or fails.
- 23Stress TestingStress testing is used to test the stability & reliability of the system
Threshold of breaking point is determined by Load Testing - 24Volume TestingHow long it takes to load large amounts of data into the database
- 25Recovery TestingTesting how well the system recovers from crashes, hardware failures or other major problems
EX: Disaster Recovery Testing (DR testing in banks) - 26DR TestingDisaster Recover Testing
Informationen
- Beschreibung
- QA Engineer QA- Fundamentals Karteikarten am Flash Cards: Testing Levels & Types, erstellt von Mircea Manu am 11/11/2021.
- Erstellt von
- Mircea Manu
- Aufrufe
- 1
- Bewertung