Please enable JavaScript.
Coggle requires JavaScript to display documents.
Testing (Non-functional (Efficiency testing (Efficiency testing - how…
Testing
Non-functional
-
Realibility testing
Reliability Testing is about exercising an application so that failures are discovered and removed before the system is deployed.
-
-
-
Efficiency testing
-
Test efficiency - (total number of defects found in unit +system)/(total number of defects found in unit+system+user acceptance testing)
Maintainability testing
Maintainability testing is very important because it shows the ability to update or modify the system under test
Portability testing
Portability testing is focused on transferring files/webpages/etc from one hardware/browser/software environment to another
Baseline testing
For making building, i need base.Need to create baseline, from which further testing is done.Same like other this sided testing methods it has nothing to do with testing of functionality of application
Baseline testing usually solves many issues at earlier stages, reduces project cost. Makes Software development life cycle little bit easier. The advantage of these tests are graphs with limited measurements where the problem transaction can be easily identified.
Compliance testing
Compliance testing determines, whether we are implementing and meeting the defined standards of company. Sometimes we need to do analysis to improve the standards
Documentation testing
Documentation is as important to a products success as the product itself. IF documentation is poor or wrong it reflects on the quality of the product and the vendor
-
-
Performance testing
Performance testing can be like a diagnostic tool for system. It can verify if a system claims manufacturer made specifications
Compatibility testing
Almost same like portability testing. Compatibility testing is used to ensure compatibility of the system/application/website with other objects such as other web browsers/ hardware platforms
Security testing
Security testing is done to check: application or product is secured or not. It checks if the application is vulnerable to attacks, if anyone hack the system or login to the application without any authorization.
-
-
Stress testing
Overload your system or load the system to its breakpoint. All system breaks and recovers should be monitored.
Recovery testing
Recovery testing is the activity of testing how well an application is able to recover form crashes, hardware failures
-
Localization testing
The main purpose of doing localization testing is to check appropriate linguistic and cultural aspects for a particular locale
Non-functional testing is testing of a software application for its non-functional requirements: the way system operates, rather then specific behaviours of that system.
Functional
Functional testing is quality assurance process. Functional testing usually describes what the system does.
-
Regression testing
Black box testing
Testing treats software under test as a black-box without knowing its code. Not so effective testing because of testers luck of knowledge about software internals
Testing that verifies that software previously developed and tested still performs correctly even after it was changed or interfaced with other software.
-
Usually regression testing is performed when changes are made to the existing functionality of the software or if there is a bug fix in the software.
Usability testing
Usability testing is technique used to evaluate a product by testing it on users. This testing gives direct input on how real users use the system.
Hallway testing
Its a cheap method of usability testing which randomly selects people and they are asked to try using the product or service
Great way to make hallway testing is to make little workplace near high foot traffic area. Your goal is to associate walkers with your project. They will need only 5-10 minutes of their day to test your project.
Remote testing
Main purpose of remote testing is to allow participants test your project in their natural job. This can be done by remote usability services and screen-sharing.
-
White box testing
White box testing is a software testing method in which design and code of the project is known to the tester. Advantage - testing can start at early stages of project. Disadvantage - highly skilled tester is needed to test like this
Ad hoc testing
-
Buddy testing - one from development team, one from test team
-
-
Exploratory testing
Exploratory testing is about exploring, finding out about the software, what it does and what it doesnt do, what works what doesnt work. Tester is making decisions about what to test next
Checklists
Checklist- is a list of tests which should be run in a definite procedure. It helps to understand if testing is fully run and how many tests failed. Test order should be strict not random
-
-
-