QA - Functional & Non-Functional :: GUI, Input, Backend, SOA, Load, Security, Performance Testing
In general, s/w testing stage is classified into below categories:
1. Usability Testing
2. Functional Testing
3. Non-functional Testing
Usability Testing: To verify cosmetic nature & user friendliness of the s/w
a) User Interface testing (UI) : Look & feel, Ease of Use, Short navigations
b) Manual support / Help documents testing: to verify existence, completeness, correctness of help docs prepared by technial writers.
***Functional Testing:
To verify project's functionalities in terms of customer requirements *Important
a) Smoke/sanity testing
b) Functionality testing
Smoke testing:
To quickly verify if the system is up and running or not and important features/functionalities are working as expected.
Should not take more than 15-30 min
After each deployment (dot releases)
***Functionality Testing:
Input: BRS documents
Apply: Website / apply
GUI (Graphical User Interface) or Behavioral coverage (all objects are getting displayed correctly)
GUI testing is also called as "Control flow testing". During this testing testing team can operate AUT/SUT screens and observe the behavior of every object (menu, checkbox, textbox, image, dropdown, screensize, icons, buttons, links, toolbar etc..) in every screen of AUT/SUT.
-Inputs Domain coverage (Input values verification) - Field validations
Test team can operate on every screen of AUT by giving different inputs to observe size (BVA) and type(ECP) of the i/p.
-Error Handling coverage (prevent / conntrol wrong operation)
Tester's job: to operate on screens by giving invalid input to check the existence of the error messages.
-Manipulations / Calculations coverage (output values verification)
Tester can operate on the screens of the application by giving valid inputs to test the correctness of the output.
Backend / Database coverage (database operations verification)
Tester can operate on frontend screens and observe the corresponding operations impact on the DB tables by means of SQL queries.
-Order of functionality (to verify order of features e.g. forget password, signup is not possible)
Tester can observe the sequential order of the objects, features, functionalities on all screens of AUT.
SOA Testing (Webservices/SOAP/Rest services/Api testing)
Tester can observe sharing of common resources among different systems/softwares (Webservices/Databases..). SOAPUI/RestAssured/ReadyApi!/Postman
Regression regression testing /End to End: to verify if the existing functionality is not broken because of a defect fix.
3. Non-functional testing (optional testing): Performance tester
Eg. Performance/Stress/Load/Endurance testing, Security, Reliability, Compatibility, Portability, Configuration/ Installation testing/ Memory testing/ Storage/ Multi-languity testing/Globalization (Internationalization/Localization)/Parallel testing, Disability testing (508)
To verify non-functional aspects such as performance, security etc. in the software if customer/management is interested (complexity/timeframe/budget)
Tools: HP Load runner, Rational Performance Tester, Neo Load test, JAZZ..
Compatibility/Portability testing - To verify whether the project working in all environment/operating systems/servers/browsers.
Configuration testing - to verify the software is configured with hardware or not.
Installation testing - to verify the installation of any software ware downloaded is proper or not.
Security testing - Authentication /Authorization / Encryption-Decryption
Authentication - validating the the user credential to connect to the software system (login)
Authorization - Admin user, normal user, supervisor, custcare user's features must appropriately be displayed
Encrypt/Decrypt: Encryption means converting original data to transmit data by applying some algorithm; Decryption means converted transfmit data to original data by applying some algorithm
Memory/Data Volume testing/ Storage:
To verify the project is able to handle maximum limit of data ( 2GB data, 1000 users info)
*Performance /Load testing: To verify application is able to handle the load of concurrent users per curstomer expections mentioned in the SLA (Service level agreement) --SLA: 90% of the time, the average response time should be 5 seconds or less and 10% of the time, the average response time should be between 5 - 10 seconds.
Number of concurrent users accesing application at the same time (500 users) 10, 50, 100, 250, 500
Stress testing/Spike : To verify the application is able to sustain the load increments.
Multilanguity testing:- Globalization (internationalization or location). Internationalization: to verify project functionalities country-wise in terms of notations, currency, date format..
Localization: to verify project functionalities with different languages
Parallel Testing/Comparative testing: to verify the previous versions of the same product as well as it's competitive product in the market