![]() ![]() On the other hand, sufficient data is required to be able to carry out a satisfactory analysis in retrospect. Sometimes the measuring in itself also puts demands on the system, which can lead to distortion of the results. It should be clearly determined in advance what and how measuring is to be done during the real-life test. These are tools that simulate, for example, the number of users through the creation of virtual users, or tools that simulate a particular loading of the back-end of the system by offering transactions directly via the database management interface (hence without the use of the front-end or network). However, use is increasingly being made of tools that simulate a realistic load in various ways. In an environment in which the number of end users is not too great, you can have everyone work overtime for a weekend and carry out a previously established test scenario. The aim here is to examine whether both the available system resources and the available time are sufficient for the (nightly / weekend) execution of big batch jobs.Įxecution of the real-life test is usually more complicated than that of other tests. The aim here is to examine whether the available system resources are sufficient for the combination of a normal number of interactive users with the simultaneous execution of relatively demanding batch jobs. This often involves a test with an increasing number of (simulated) users. The aim here is to examine what the maximum load is under which the system will still perform to an acceptable level. Measuring the breaking point (stress testing).This often involves a test with a maximum number of users who carry out interactive work (peak loading) or a test in which certain transactions are carried out often and at length. The aim here is to examine whether there are sufficient system resources for even the most stressful, but realistic, circumstances. This often involves a test with an average number of users who carry out interactive work, run overviews and carry out a number of small batch functionalities. The aim here is to examine whether the available system resources are sufficient for the usual circumstances. ![]() A particular loading of the system is simulated by carrying out realistic scenarios.Ī profile is used in the setting out of one or more test goals of the real-life test. In practice, in a real-life test a mix of these profiles is often used. Simulation of a realistic loading of the system in terms of numbers of users and/or transactions.įor further explanation of these profiles and their simulation, refer to " Statistical usage: Operational profiles and load profiles". Simulation of the realistic usage of the system, by carrying out a sequence of transactions, which is compiled in a statistically responsible way. This also serves as a test basis and, in this context, is often referred to as the profile. To be able to test whether a system can handle realistic usage of it, that usage should be somehow specified. Insufficient capacity of peripherals and data-communication network.Insufficient memory or storage space available.Inadequate response times and speed of processing.Crashing of transactions that are carried out in a particular sequence.Crashing of transactions following lengthy use.Many defects that are found with a real-life test are connected with a system's use of resources: This test mainly focuses on characteristics, such as effectivity, connectivity, continuity and performance of the system under test. With the real-life test (RLT), it is not the intention to test the system behaviour in separate situations, but to simulate the realistic usage of the system in a statistically responsible way. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |