A performance testing application system

Abstract

The present invention relates to a system (1) which enables performance testing, a test that shows how software works under certain conditions and under the desired workload and performance thereof, to be performed by means of interfaces provided on an application (3) without the need to write codes.

Description

[0001] A PERFORMANCE TESTING APPLICATION SYSTEM

[0002] Technical Field

[0003] The present invention relates to a system which enables performance testing, a test that shows how software works under certain conditions and under the desired workload and performance thereof, to be performed by means of interfaces provided on an application without the need to write codes.

[0004] Background of the Invention

[0005] Software performance testing is a test to evaluate how a software application or system performs under certain conditions and how the application behaves under that load. Performance testing is performed with the aim of measuring and analysing the performance characteristics such as speed, response time, scalability, resource usage and overall processing capacity of the software. Performance testing is subdivided into subgroups such as load testing, which measures how the system behaves under a given load, when the number of users or workload increases; endurance testing, which shows the behaviour of the system under continuous load for a given period of time; stress testing, which determines at what point the system will fail by pushing its maximum capacity; performance measurement, which measures how certain metrics (e.g., processing speed, response time, memory usage) change in the behaviour of the system under a given load or customer load; scalability testing, which measures how the system behaves when system resources are increased or decreased; stability testing, which measures how stable it remains when operating under long-term load; and database performance testing, which shows how much database queries and transactions affect speed. The said tests are usually performed as part of the software development process and provide important information about how the software will perform when used by users in the real world. Performance testing helps to identify potential performance issues, use system resources efficiently and optimize the user experience.

[0006] The performance of software applications is of great importance in terms of providing the expected service to users. For this reason, performance testing is a necessary test to ensure that the software applications perform as expected under the desired workload. The purpose of performance testing is not to find errors, but to eliminate performance bottlenecks by identifying them.

[0007] Performance testing reduces development time and infrastructure costs by finding potential problems in critical applications before the customer does. However, existing performance testing tools have some shortcomings. For example, some tools require writing performance testing by writing code, which may result in a more time-consuming process for developers and may be more prone to user error. By overcoming these shortcomings, performance testing tools can become more effective, and the performance of software applications can be improved further.

[0008] For this reason, considering the studies and deficiencies included in the current technique, it is understood that there is a need for a system a system which enables performance testing to be made more practical for users by creating performance testing according to user needs with no code.

[0009] The United States patent document no. US6269474B1, an application included in the state of the art, discloses an optimization system including an option to convert existing code to a code-less environment or to create a codeless environment by the establishment of all essential application elements in files. In the said invention, the code-less environment is created through a design and analysis step, an environmental step and an installation step. An application map is prepared during the design and analysis step which defines where information enters into the system, where information is used, and where used information is changed. The application map is also used to verify that all information is accounted for. The design and analysis step also includes the generation of default database structures, screen formats, print layouts, file transfer protocols, validation tables and communication specifications. The environmental step includes modifying specifications in accordance with user preferences, simulating performance of the specifications with test data, preparing existing data files for conversion to the code-less system, and implementing parallel processing.

[0010] Summary of the Invention

[0011] An object of the present invention is to realize a system which enables performance testing, a test that shows how software works under certain conditions and under the desired workload and performance thereof, to be performed by means of interfaces provided on an application without the need to write codes.

[0012] Another object of the present invention is to realize a system which enables users to create and edit test packages and scenarios, to run the created test scenarios and to view the test results without the need to write code by selecting the application, network or software they want to perform performance testing on.

[0013] A further object of the present invention is to realize a system which enables recommendations to be offered in order to provide a simulation of real user behaviour.

[0014] Detailed Description of the Invention

[0015] “A Performance Testing Application System” realized to fulfd the objectives of the present invention is shown in the figure attached, in which: Figure 1 is a schematic view of the inventive system.

[0016] The components illustrated in the figure are individually numbered, where the numbers refer to the following:

[0017] 1. System

[0018] 2. Electronic device

[0019] 3. Testing application

[0020] 4. Application server

[0021] The inventive system (1) which enables software performance testing to be performed without the need to write code comprises at least one electronic device (2) which is configured to exchange data by using any communication protocol and to run at least one application thereon; at least one testing application (3) which is run on the electronic device (2) and is configured to enable users to create test scenarios through the provided interfaces by entering information regarding the environment in which they want to perform performance testing, to perform performance tests by running the created scenarios and to view the test results; and at least one application server (4) which is configured to process user requests entered through the testing application (3) by receiving them; to run the test scenarios created by the users on the testing application (3) by accessing the environment (application, software, network, server) in which the user wants the performance testing to be performed; and to present the test results to the users through the testing application (3) by converting them into reports.

[0022] The electronic device (2) included in the inventive system (1) is a device in the form of a smartphone, tablet computer, desktop computer or portable computer configured to run at least one testing application (3) thereon. The said electronic device (2) has speakers for providing audio output, at least one camera capable of taking images, and an input unit in the form of a key or touch screen. The electronic device (2) is configured to enable users to access the testing application (3).

[0023] The testing application (3) included in the inventive system (1) is run on the electronic device (2) and is configured to enable users to perform performance testing and carry out performance testing processes without the need to write code. The said testing application (3) is configured to enable users to create test scenarios by selecting the environment on which they want to perform performance testing, in the form of servers, applications, databases and networks, and to run the created scenarios. In the preferred embodiment of the invention, the testing application (3) is configured to provide interfaces adapted to allow users to create test tasks consisting of test packages comprising test cases, to edit created test tasks, to preview created test tasks, to perform test operations with created tasks and to view test results. The testing application (3) is configured to provide at least one interface adapted to allow users to create a test file for the test they want to run by entering information in the form of client, data set, test task name and task type. The testing application (3) is configured to provide at least one interface adapted to allow users to add to the test tasks (scenarios) they create from existing test cases; add test collections, the small set of tests within a task that are used if a test needs to be performed before a test or if one wants to extract a value from the output of a test and use it in another test; and to add query parameters, header and body parameters. The said testing application (3) is configured to provide at least one interface adapted to allow users to add headers by entering data in the form of header name and header value when creating the test task and to update the added headers. The testing application (3) is configured to provide at least one interface adapted to allow users to add body information by entering the required information when creating the test task and to update the added body sections. The said testing application (3) is configured to provide at least one interface adapted to allow users to view how to send test cases and their output by testing the test cases they have added to the test task. The testing application (3) is configured to provide at least one interface adapted to allow users to preview the created test tasks and to determine the weight and waiting times for each of the prepared test cases. The testing application (3) is configured to provide at least one interface adapted to allow users to view the created test tasks and to create a request for the test task of their choice to be automatically run at the specified time and / or by being triggered by the user by determining the number of machines on which the test is to be run and the data center. The testing application (3) is configured to provide at least one interface adapted to allow users to view test tasks and results that have been run in the past, to edit created tests, to share them with other users and to run them again. The testing application (3) is configured to enable users to start the test by entering the number of users with which the test is to be run, and the number of users started per second.

[0024] The application server (4) included in the inventive system (1) is configured to process user requests entered through the testing application (3) by receiving them. The application server (4) is configured to run the test scenarios created by the users on the testing application (3) by accessing the environment (application, software, network, server) in which the user wants the performance testing to be performed; and to present the test results to the users through the testing application (3) by converting them into reports.

[0025] Industrial Application of the Invention

[0026] In the inventive system (1) users are enabled to create test scenarios and perform performance testing by entering performance test parameters without the need to write code for any software, application or network environment on which they want to perform performance testing. By means of the said system (1), developer users are enabled to take precautions for errors that may occur by simulating heavy traffic for application, software or network performance in advance and to reduce the infrastructure costs that will be spent for testing.

[0027] Within these basic concepts; it is possible to develop various embodiments of the inventive “A Performance Testing Application System (1)”; the invention cannot be limited to examples disclosed herein and it is essentially according to claims.

Claims

CLAIMS1. A system (1) which enables software performance testing to be performed without the need to write code; comprising at least one electronic device (2) which is configured to exchange data by using any communication protocol and to run at least one application thereon; and characterized by at least one testing application (3) which is run on the electronic device (2) and is configured to enable users to create test scenarios through the provided interfaces by entering information regarding the environment in which they want to perform performance testing, to perform performance tests by running the created scenarios and to view the test results; and at least one application server (4) which is configured to process user requests entered through the testing application (3) by receiving them; to run the test scenarios created by the users on the testing application (3) by accessing the environment (application, software, network, server) in which the user wants the performance testing to be performed; and to present the test results to the users through the testing application (3) by converting them into reports.

2. A system (1) according to Claim 1; characterized by the electronic device(2) which is a device in the form of a smartphone, tablet computer, desktop computer or portable computer configured to run at least one testing application(3) thereon.

3. A system (1) according to Claim 1 or 2; characterized by the electronic device (2) which has speakers for providing audio output, at least one camera capable of taking images, and an input unit in the form of a key or touch screen.

4. A system (1) according to any one of the preceding claims; characterized by the electronic device (2) which is configured to enable users to access the testing application (3).

5. A system (1) according to any one of the preceding claims; characterized by the testing application (3) which is run on the electronic device (2) and is configured to enable users to perform performance testing and carry out performance testing processes without the need to write code.

6. A system (1) according to any one of the preceding claims; characterized by the testing application (3) which is configured to enable users to create test scenarios by selecting the environment on which they want to perform performance testing, in the form of servers, applications, databases and networks, and to run the created scenarios.

7. A system (1) according to any one of the preceding claims; characterized by the testing application (3) which is configured to provide interfaces adapted to allow users to create test tasks consisting of test packages comprising test cases, to edit created test tasks, to preview created test tasks, to perform test operations with created tasks and to view test results.

8. A system (1) according to any one of the preceding claims; characterized by the testing application (3) which is configured to provide at least one interface adapted to allow users to create a test file for the test they want to run by entering information in the form of client, data set, test task name and task type.

9. A system (1) according to any one of the preceding claims; characterized by the testing application (3) which is configured to provide at least one interface adapted to allow users to add to the test tasks they create from existing test cases; add test collections, the small set of tests within a task that are used if a test needs to be performed before a test or if one wants to extract a value from the output ofa test and use it in another test; and to add query parameters, header and body parameters.

10. A system (1) according to any one of the preceding claims; characterized by the testing application (3) which is configured to provide at least one interface adapted to allow users to add headers by entering data in the form of header name and header value when creating the test task and to update the added headers.

11. A system (1) according to any one of the preceding claims; characterized by the testing application (3) which is configured to provide at least one interface adapted to allow users to add body information by entering the required information when creating the test task and to update the added body sections.

12. A system (1) according to any one of the preceding claims; characterized by the testing application (3) which is configured to provide at least one interface adapted to allow users to define variables for information in fields such as header and body when creating a test task.

13. A system (1) according to any one of the preceding claims; characterized by the testing application (3) which is configured to provide at least one interface adapted to allow users to view how to send test cases and their output by testing the test cases they have added to the test task.

14. A system (1) according to any one of the preceding claims; characterized by the testing application (3) which is configured to provide at least one interface adapted to allow users to preview the created test tasks and to determine the weight and waiting times for each of the prepared test cases.

15. A system (1) according to any one of the preceding claims; characterized by the testing application (3) which is configured to provide at least one interface adapted to allow users to view the created test tasks and to create a request for thetest task of their choice to be automatically run at the specified time and / or by being triggered by the user by determining the number of machines on which the test is to be run and the data center.

16. A system (1) according to any one of the preceding claims; characterized by the testing application (3) which is configured to provide at least one interface adapted to allow users to view test tasks and results that have been run in the past, to edit created tests, to share them with other users and to run them again.

17. A system (1) according to any one of the preceding claims; characterized by the testing application (3) which is configured to enable users to start the test by entering the number of users with which the test is to be run, and the number of users started per second.

18. A system (1) according to any one of the preceding claims; characterized by the testing application (3) which is configured to allow users to schedule or run a test at a later date by entering the number of users and the date they want to start the test.

19. A system (1) according to any one of the preceding claims; characterized by the application server (4) which is configured to process user requests entered through the testing application (3) by receiving them.

20. A system (1) according to any one of the preceding claims; characterized by the application server (4) which is configured to run the test scenarios created by the users on the testing application (3) by accessing the environment in which the user wants the performance testing to be performed; and to present the test results to the users through the testing application (3) by converting them into reports.

Images