ISBN : 978-81-963532-2-3 (E-Book) In each of the above types of tests, various kinds of test cases are designed by referring to theSRS document. Broadly, these tests can be classified into functionality and performance tests.The functionality test tests the functionality of the software to check whether it satisfies thefunctional requirements as documented in the SRS document. The performance test tests theconformanceof thesystem with thenonfunctional requirements of thesystem. PerformanceTesting Performancetestingiscarriedouttocheckwhetherthesystemneedsthenon-functionalrequirements identified in the SRS document. There are several types of performance testing.Among of them nine types are discussed below. The types of performance testing to be carriedoutonasystemdependonthedifferentnonfunctionalrequirementsofthesystemdocumentedintheSRS document. All performancetests can beconsidered as black-boxtests. • Stresstesting • Volumetesting • Configurationtesting • Compatibilitytesting • Regressiontesting • Recoverytesting • Maintenancetesting • Documentationtesting • Usabilitytesting StressTesting-Stresstestingisalsoknownasendurancetesting.Stresstestingevaluates system performance when it is stressed for short periods of time. Stress tests areblack box tests which are designed to impose a range of abnormal and even illegal inputconditions so as to stress the capabilities of the software. Input data volume, input datarate, processing time, utilization of memory, etc. are tested beyond the designed capacity.For example, suppose an operating system is supposed to support 15 multi programmedjobs, the system is stressed by attempting to run 15 or more jobs simultaneously. A real-time system might be tested to determine the effect of simultaneous arrival of severalhighpriorityinterrupts. Stress testing is especially important for systems that usually operate below the maximumcapacity but are severely stressed at some peak demand hours. For example, if the non-functional requirement specification states that the response time should not be more than20 secs per transaction when 60 concurrent users are working, then during the stresstestingthe response timeischecked with 60 usersworkingsimultaneously. 106 Software Engineering Keerthana P, Manasa KN, Ganga D Bengal
112 Publizr Home