-Performance testing of multi-user software systems is typically performed by emulating activities of multiple users working with the system simultaneously. These virtual users collect performance measures like response time and correctness while loading the system during the test. During a typical load scenario number of simultaneous virtual users gradually increases from one to some intended maximum, allowing to find out statistical relation between number of simultaneous users and performance measures.However having fixed load scenario has several drawbacks. Usually the test has to be repeated iteratively with adjusted load scenarios, taking into account results acquired from previous test iterations. As load scenarios have to be adjusted manually and repetitions of the test may take considerable time, this approach seems to be ineffective. This paper presents an alternative approach, where load scenario is adjusted automatically during the test, taking into account performance measures already gathered in the same test. Drawbacks of fixed load scenarios are analysed and methods of eliminating them by automatic adjustment are described. A case study showing implementation of the method and results obtained by applying it to performance testing of a real system is provided.
Problems of test-driven aspect-oriented developmentTest-driven development and aspect-oriented programming are relatively new development techniques each having its own benefits. However, using aspect-oriented language like AspectJ in test-driven development leads to new types of problems that do not appear if these two approaches are applied separately. These problems arise mainly because aspect-oriented paradigm breaks encapsulation principle - behaviour of class is not implemented just in class itself like in traditional object-oriented programming but can be heavily affected by many external aspects. Traditional unit tests designed to test a single unit are not sufficient any more because behaviour being tested is distributed through several units at once, so test design becomes more complicated. In order to efficiently use these two techniques together such problems have to be identified and ways to workaround them have to be discovered. This paper focuses on those problems, describing the most notable ones. Problem descriptions are based on experience with AspectJ, but most of them are common to any aspect-oriented language with similar features. Some empirically discovered principles are provided that help softening negative impact of those problems.
scite is a Brooklyn-based organization that helps researchers better discover and understand research articles through Smart Citations–citations that display the context of the citation and describe whether the article provides supporting or contrasting evidence. scite is used by students and researchers from around the world and is funded in part by the National Science Foundation and the National Institute on Drug Abuse of the National Institutes of Health.
hi@scite.ai
10624 S. Eastern Ave., Ste. A-614
Henderson, NV 89052, USA
Copyright © 2024 scite LLC. All rights reserved.
Made with 💙 for researchers
Part of the Research Solutions Family.