Abstract—Software Testing is one parts in Software Engineering whatever your development model. For Software quality assurance, we may need Functional Test, Non-Functional Test or both. Load Testing is one kind of Performance Test which belongs to Non-Functional Test. And Load Testing is the most frequently-executed testing type in Performance Test because it’s relevant to us. For example, the ticket-booking website may fail or crash as soon as a Lady Gaga concert begins to sell. In this case, the sudden huge number of users (equivalent to heavy loads) may slow down the system, causing some transactions to become failed and even crash the system if it doesn’t have Load Testing before the website gets online. This can cause huge loss whatever in business revenues or reputations. As you can see, it’s so important to understand your system’s max loading before it goes to production environment, because system providers still have chance to do performance tuning to improve the system quality. Besides, I notice that there are almost no articles on the Internet which provide the practical steps or complete process for Load Testing. In view of this, I’ve summarized the 4 steps for proceeding Load Testing which can be used both by testers or system providers.
Index Terms—Soak test, spike test, configuration testing, closed rule for website. isolation testing, transaction response time, successful transaction rate, fail-open, fail-closed.
Chen Yiju is with the Institute for Information Industry, Taiwan (e-mail: wichchen@yahoo.com.tw).
[PDF]
Cite:Chen Yiju, "Working Experiences of Planning, Design and Implementation for Software Load Testing," International Journal of Knowledge Engineering vol. 3, no. 1, pp. 13-16, 2017.
