Software testing methodology and platform.

TR202418658A1Pending Publication Date: 2026-06-22COMMENCİS TEKNOLOJİ ANONİM ŞİRKETİ
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
TR202418658
Authority / Receiving Office
TR · TR
Patent Type
Applications
Current Assignee / Owner
Filing Date
2024-12-12
Publication Date
2026-06-22

Smart Images

  • Figure 00000016_0000
    Figure 00000016_0000
  • Figure 00000016_0001
    Figure 00000016_0001
Patent Text Reader

Abstract

The invention relates to a method for determining the optimal order in which the fewest possible number of test scenarios, created for software developed on different platforms, can be run, and a remote test scenario execution platform that utilizes this method. The invention relates specifically to a software testing method and platform that includes a database, interface, server, virtual machine, and virtual database within a virtual machine, and a virtual server.
Need to check novelty before this filing date? Find Prior Art

Description

1 TARIFF SOFTWARE TESTING METHOD AND PLATFORM The technical field to which the invention relates: The invention is a test created for software developed on different platforms. Which of the following 5 test scenarios is most suitable, from the fewest possible number of scenarios? a method to ensure sequential running and a remote test using this method The scenario is related to the running platform. The invention, in particular, relates to databases, interfaces, servers, virtual machines, and virtual machines within virtual machines. The database relates to a software testing method and platform that includes a virtual server. State of the art: 10 Creating software tests and test scenarios, allowing users to log in to the platform and access appropriate content. mobile / web application platforms, software that enable them to perform tests These platforms have become indispensable tools in the development process. These platforms are used for software... to improve quality, enhance user experience and minimize potential errors It is used for this purpose. 15 One of these platforms allows users to easily create test scenarios and It has user-friendly interfaces that allow for management. Developers and testers Experts systematically define the scenarios needed to test specific functions. They can create a testing process. This saves time and makes the tests more organized. and ensures that it is done effectively. 20 Users can log in to the platform and run test scenarios, enabling the software to... This allows for testing with real user experience. Such applications, By following specific scenarios, users can ensure the software delivers the expected functionality. This allows them to evaluate what it does not offer. User feedback, It is extremely valuable in terms of software development. 25 These platforms, which offer automation features, can automate repetitive test scenarios. By doing so, it increases efficiency. This speeds up testing processes and reduces manual labor. This helps reduce the probability of errors. Users can automate test scenarios. 2 It can be run as is, and the results can be reviewed instantly for a quick assessment. is able to do so. User experience plays a critical role in the success of software. Mobile / web Application platforms use various surveys to gather user feedback, and It provides evaluation forms. This feedback helps us determine how the software meets user needs. It plays a major role in shaping the system and is a valuable resource for development teams. It constitutes. In addition, these platforms often offer cloud-based services, allowing users to... It allows access from anywhere. Users can access it via mobile or web. By logging into the platform through their browsers, they can easily run test scenarios. and they can track the results. This flexibility makes testing processes more dynamic. It brings. In conclusion, mobile / web applications that generate software testing and test scenarios. platforms play an important role in improving the quality of software development processes. These platforms encourage active user participation, resulting in software that is 15 years old. It helps to understand how the system performs from a user perspective. In the known state of the art, there are various recommendations for software testing methods and platforms. Although applications have been developed, these improvements are insufficient. For this purpose... Some of the applications related to the developed inventions are given below. Patent application number “US10140206B2”, which exists in the known state of the art, 20 a "service" designed to make software testing processes more effective It offers a "pilot" system. This system allows multiple software programs to be run through a server. It allows pilot tests for the product to be carried out simultaneously. A system that allows corporate and entry-level clients to register in advance. Along with the function, there is an indicator where these clients can view their test results. 25 It also includes a panel. Thus, software development can be carried out with the participation of different clients. The efficiency of proof-of-concept testing in the process is increased, and resource utilization is optimized. and feedback processes are being accelerated. Patent number “CN113886262A” exists in the known state of the art. In its application, it proposed a method 30 aimed at optimizing automated software testing processes. 3 and device development is mentioned. Specifically, when an automated test request is received. predefined according to the software to be tested and the specified test scene. the test process using an RPA (Robotic Process Automation) test execution script This method enables the implementation of regular and repetitive workflows using RPA. While running the process through the script, the AI ​​components also simulate manual testing processes. By doing so, it aims to increase the efficiency of automated tests. As a result, this The invention saves time and resources in software testing processes while improving test quality. It also aims to improve. Patent application number “CN112486812A”, which exists in the known state of the art, It describes a cloud-based distributed framework software testing method and appliance. 10 Essentially, numerous methods are used to make software testing processes more efficient. It allows the test case to be executed in parallel. First, a test command. By collecting this data, the user change code, base code, and test case information are obtained. Furthermore... Then these codes are combined and compiled to create a combined code. Test case. The number and necessary computing resources are determined, and test 15 is conducted using these resources. The cases are processed in parallel. Once the results are obtained, the relevant system... With this information, the software testing process is completed. This method involves testing a computer. It aims to increase software testing efficiency by overcoming its limitations. Patent application number “EP3905051A1”, which exists in the known state of the art, It relates to a method and system aimed at automating software testing processes. 20 Automatic generation of test scenarios and automation scripts. The system focuses on recording the details of the application at the micro level, page by page. It creates an index based on navigation. A mind map using traversal algorithms. or by creating a tree structure, it defines the necessary test scenarios. Additionally, all basic screens... By capturing its features and tags, it links this information to an integrated action library. 25 In conclusion, manual testing processes can save time and effort. It makes automation possible. In the current state of the art, end users who order software also receive the products. Test plans for acceptance tests they conducted when they received the progress on the project. to create, test, and test a certain portion of the scenarios they will choose from. 30 and that allows it to compare with previous versions and while doing this, the machine also includes information about which version of the software it will be tested against. 4 Selection from a pool of test scenarios using learning-based algorithms with information on the minimum required scenario and the order in which they should be run it will provide the user with and, if the user wishes, these written test scenarios will be automatically executed. To start the test, you can manually test remotely by selecting the relevant version through the platform. artificial intelligence (AI) can perform and analyze and prioritize test scenarios. There is a need for an intelligence-based deep machine learning testing method and platform. It is heard. In conclusion, due to the negative aspects described above and the current solutions, the subject matter... Due to its shortcomings, an improvement is needed in the relevant technical field. It has been made. 10 The purpose of the invention: The main goal of the invention is to offer a more flexible structure and to adapt test scenarios in each case. dynamically analyze software changes and suggest the most suitable scenarios. to provide. 15 Another aim of the invention is to extract information by analyzing the changes between the two versions. In impact analysis, changes to the code are identified both directly and indirectly. The test scenarios that could have an impact, in what order should they be run for the most efficient testing process? The selected tests were analyzed through an analysis process to determine their likelihood of occurring. The aim is to ensure that the test scenarios are arranged in order. Thus, 20 test scenarios can be run smoothly. The necessary tests are also included in the scenario, and then the final ranked list is created. This ensures that the test plan is communicated to the end user. Another purpose of the invention is to analyze code changes between different versions of the software. The aim is to optimize testing processes by doing so. Thus, software development It saves time and money by reducing the testing load in the processes. 25 Another aim of the invention is to provide a user-centric testing process for the software to end users. The aim is to enable analysis of how it is perceived and evaluated by others. Another goal of the invention is to use machine learning and artificial intelligence algorithms. The goal is to enable the analysis and prioritization of test scenarios. This allows for software testing. This demonstrates that it offers a more specialized and focused solution in the field of automation. 30 Another purpose of the invention is to allow end-user test scenarios to directly integrate the software with the customer. The aim is to provide solutions that can be incorporated into acceptance processes. Thus, dynamic and with a user-centric approach to creating test scenarios, software development It offers a viable solution at every stage of the processes and software output. Any profile provides the capability to run end-to-end tests remotely. 5 Another purpose of the invention is to test by analyzing the changes in each version of the software. The aim is to make the processes more dynamic. Thus, software testing processes become more efficient. It enables making it effective and fast. Another purpose of the invention is to address the issues arising from machine learning and artificial intelligence studies. With the methods we have established, we aim to increase the efficiency of this testing process. The aim is to ensure that only the tests that are truly needed are run. It also provides information on the order in which the runs should be performed, by sharing this information with the user. This ensures that potential errors are detected as quickly as possible. Explanation of the figures: FIGURE -1; This is a system diagram illustrating the software testing method and platform for the invention. 15 FIGURE 2; Diagram showing the invention software testing method and platform. It is a drawing. Reference numbers: 1: Database 2: Interface 20 3: Server 4: Virtual machine 4.1: Virtual Database 4.2: Virtual Server 5: Go 25 6 6: Docker Unit 100: The test team prepares the test scenarios. 110: Uploading prepared test scenarios via the interface 120: Testing scenarios using machine learning and artificial intelligence algorithms 5 to be analyzed 121: Two versions marked as version transition on the version control system. scanning for all code changes between them 122: Indexing all scanned files in the database. 123: For each file that has been changed, use the dependencies in the file contents to perform a search. Creating an addiction map 10 124: By combining these dependency maps for all files, all changes to the project are made. combining the parts on a single map 125: All classes on this map are based on previously created source code analysis. Completing the impact analysis by scanning through the index. 126: Test referenced by analyses by identifying analyses that may be affected 15 determining scenarios 127: These test scenarios, along with mandatory test scenarios, are combined to conduct the test. sending the scenario to the prioritization module 130: Sending prioritized and reduced test scenarios to the virtual machine. 131: Prioritizing test scenarios 20 131.1: Document topic matrix using topic modeling algorithm via Docker creation 131.2: Receiving the prepared test scenarios 7 131.3: Test scenarios using document matrix through machine learning prioritization 132: Reducing test scenarios 132.1: Apache Lucene / Elasticsearch, source code history, and the project via JIRA. Version, changes made, and bug fixes data collection 5 132.2: Testing the collected data through machine learning algorithms reducing scenarios 140: Virtual database of prioritized and reduced test scenarios. recording 150: Performing the test with a virtual machine 10 151: The virtual machine retrieves the project and partitions from the database. 152: Retrieving test scenarios from a virtual database 153: Creating automatic partitions in a virtual machine 154: Retrieving coverage data from the virtual database 155: Retrieving project versions from the virtual database 15 156: Virtual database and server-side automated scenarios via virtual server to be found 157: Retrieving test scenarios from a virtual database 158: Running the tests 160: Generating the test report 20 170: Saving the report to the Docker unit. 180: Finding the desired version in Git using machine learning. 8 190: Downloading the project from Git to the Docker unit 200: Automated test scenarios located on the virtual machine are placed in the docker unit of the machine. learning and project control 210: The project downloaded to the Docker unit and the saved report are sent via the server. 5 displayed on the interface Description of the invention: The invention, in broad terms, is for software developed on different platforms. from the created test scenarios, the fewest possible number of test scenarios generally, database (1), interface (2), server which ensures that it is run in the most suitable order. (3) and the virtual machine (4) that enables the test to take place and 10 inside the virtual machine (4) including virtual database (4.1) and virtual server (4.2) and Git (5) and Docker unit (6) It is an integrated software testing method and platform. The database (1) is the element where the project is located and which works integrated with the virtual machine (4). The interface (2), virtual machine (4) and server (3) are integrated and the project and report It is the element that is displayed. 15 The server (3) is the element that acts as a link between the docker unit (6) and the interface (2). Virtual machine (4), reduced and prioritized testing via interface (2). scenarios are transmitted, tests are carried out and it contains a virtual database (4.1) and virtual server (4.2) is the element it contains. The virtual database (4.1) contains 20 reduced and prioritized test scenarios. and the virtual machine (4) containing information about the project and the server It is a component that has an integrated circuit. The virtual server (4.2) is located within the virtual machine (4) and the virtual database (4.1) It is an integrated element. 9 Git (5) is integrated with the virtual machine (4), downloaded to the project's docker hub (6) and a version control used to track changes in computer files It is a component. The Docker unit (6) records the test report that takes place on the virtual machine (4) and Git (5) is the element from which the project is downloaded. 5 The invention allows for dynamic analysis of scenarios with each software change and optimizes them. The goal is to enable the suggestion of suitable scenarios. The analysis of changes between the two versions. In the impact analysis conducted, the direct and indirect effects of the changes to the code were determined. The test scenarios that have been identified as having an impact, in what order should they be run to maximize their effect? The 10 were selected after running an analysis process to determine if an efficient testing process would take place. It ensures the sequencing of tests. Thus, the test scenarios are executed smoothly. The final result is obtained by including the necessary tests for the scenario to be run. It enables the delivery of the test plan to the end user via a ranked list. The invention allows the developed software to undergo both user acceptance testing and a test of their desired specifications. The development package was tested on three different platforms: web, iOS, and Android for 15 days. This makes it possible for them to do so. In this way, both with the test sequencing flow... It aims to optimize the effort on the manual side as well as test automation. The workflow allows all tests of the existing software to be run automatically, and It enables the reporting of results. Thus, it allows for the request of software development. corporate clients who use user 20 as part of the software lifecycle It enables them to automate acceptance tests. The invention uses machine learning and artificial intelligence algorithms to test scenarios. It enables analysis and prioritization and is used in the field of software test automation. This shows that it offers a more specific and focused solution. The invention allows for direct integration of end-user test scenarios into the software's customer acceptance processes. It enables the provision of solutions that can be included and is dynamic and user-oriented. with a test case creation approach, at every stage of the software development process. It offers a viable solution. Thus, the software output can be customized to any profile. It provides the capability to run end-to-end tests remotely. The software testing method includes the following steps:  The test team prepares the test scenarios (100),  Uploading the prepared test scenarios via the interface (110),  Testing using machine learning and artificial intelligence algorithms analysis of scenarios (120), 5  Prioritized and reduced test scenarios are run on the virtual machine sending (130),  Prioritized and reduced test scenarios in a virtual database recording (140),  Performing the test with a virtual machine (150), 10  Creation of the test report (160),  Saving the report to the Docker unit (170),  Finding the desired version in Git by machine learning (180),  Downloading the project from Git to the Docker unit (190),  Automated test scenarios located on the virtual machine are in the Docker unit (15). Project control using machine learning (200),  The project downloaded to the Docker unit and the saved report are transmitted via the server. display on the interface (210). Machine learning and artificial intelligence algorithms, which are process steps in software testing. Analyzing test scenarios using (120) the following steps 20 includes;  Version control systems (git, Gerrit, bitbucket, etc.) as version transitions Scanning all code changes between the two marked versions (121),  Indexing of all scanned files in the database (122),  For each file that has been changed, use the dependencies in the file content to create a 25 creating an addiction map (123),  By combining these dependency maps for all files, all changes to the project are made. combining its parts on a single map (124),  All classes on this map are based on previously created source code analysis. Completion of impact analysis by scanning through the index (125), 30 11  Tests referenced by analyses by identifying analyses that may be affected. determination of scenarios (126),  By combining these test scenarios, along with mandatory test scenarios. sending the test scenario to the prioritization module (127). Prioritized and reduced testing 5, which are steps in the software testing methodology process. Sending scenarios to the virtual machine (130) follow these steps includes;  Prioritization of test scenarios (131),  Reduction of test scenarios (132). Prioritized and reduced testing, which are process steps in the software testing methodology, 10. (130) The process step is sending the test scenarios to the virtual machine. Prioritization (131) includes the following steps;  Document topic matrix using topic modeling algorithm via Docker creation (131.1),  Obtaining the prepared test scenarios (131.2), 15  Test scenarios using a document matrix via machine learning prioritization (131.3). Prioritized and reduced testing are process steps in the software testing methodology. (130) The process step is sending the test scenarios to the virtual machine. Reduction (132) includes the following steps; 20  Apache Lucene / Elasticsearch, source code history, and the project via JIRA Collection of version, changes made, and corrected bug data (132.1)  Testing the collected data through machine learning algorithms reduction of scenarios (132.2). The software testing method step is the virtual machine testing (150) 25 This includes the following steps:  The virtual machine retrieves the project and sections from the database (151),  Obtaining test scenarios from the virtual database (152), 12  Automatic partition creation in the virtual machine (153),  Obtaining coverage data from the virtual database (154),  Obtaining project versions from the virtual database (155),  Virtual database and automated scenarios via virtual server (156), 5  Obtaining test scenarios from the virtual database (157),  Running the tests (158).

Claims

13 REQUESTS 1. It is a server-based software testing platform, and its features include:  Enabling the system to interact with the user and to prepare projects and reports. an interface that enables its display (2),  The database (1) where the project is located and which works integrated with the virtual machine (4), 5  A server (3) that acts as an intermediary between the interface and the docker unit (6),  A virtual machine that enables the running of tests (4),  Reduced and prioritized within the virtual machine (4) a virtual database in which scenarios are recorded (4.1),  10 located within the virtual machine (4) and integrated with the virtual database (4.1) a running virtual server (4.2),  Integrated with the virtual machine (4), downloaded to the project's docker unit (6) and a version used to track changes in computer files Git (5), which is the control element,  The docker unit (6) where the report is saved and the project is downloaded from Git (5) 15 It includes.

2. This is a software testing method, the characteristic of which is;  The test team prepares the test scenarios (100),  Uploading the prepared test scenarios via the interface (110),  Testing using machine learning and artificial intelligence algorithms (120)  Prioritized and reduced test scenarios are run on the virtual machine sending (130),  Prioritized and reduced test scenarios in a virtual database recording (140), 25  Performing the test with a virtual machine (150),  Creation of the test report (160),  Saving the report to the Docker unit (170),  Finding the desired version in Git by machine learning (180),  Downloading the project from Git to the Docker unit (190), 30  Automated test scenarios located on the virtual machine are in the Docker unit Project control using machine learning (200), 14  The project downloaded to the Docker unit and the saved report are on the server. (210) includes the steps of the process, which is displayed on the interface.

3. This is a software testing method compliant with Claim 2, characterized by its use of machine learning and artificial intelligence. Analyzing test scenarios using intelligence algorithms (120) In the following step; 5  Two versions marked as version transitions on the version control system Scanning all code changes between versions (121),  Indexing of all scanned files in the database (122),  For each file that has been changed, use the dependencies within the file content. Creating a dependency map (123), 10  By combining these dependency maps for all files, the project's changing structure is optimized. combining all parts on a single map (124),  All classes on this map are based on previously created resources. Completing the impact analysis by scanning through the code-analysis index. (125), 15  By identifying the analyses that may be affected, the analyses have been referenced. determination of test scenarios (126),  These test scenarios, along with mandatory test scenarios, have been determined. combined and sent to the test scenario prioritization module (127) includes the steps of the process. 20 4. This is a software testing method compliant with Claim 3, and its characteristic is: Version control system. All code between two versions marked as version transition. Scanning of changes (121) process step; git, Gerrit, bitbucket etc. It includes version control systems.

5. This is a software testing method compliant with Claim 2, characterized by being prioritized and 25 Sending reduced test scenarios to the virtual machine (130) process step;  Prioritization of test scenarios (131),  Reducing test scenarios (132) involves the following steps.

6. A software testing method that complies with Claim 2 or Claim 3, and whose characteristic is: test 30 Prioritization of scenarios (131) process step;  Document topic matrix using topic modeling algorithm via Docker creation (131.1),  Obtaining the prepared test scenarios (131.2),  Testing using a document matrix via machine learning Prioritization of scenarios (131.3) includes the steps of the process. 5 7. A software testing method that complies with Claim 2 or Claim 3, and whose characteristic is; testing reducing scenarios (132) process step;  Apache Lucene / Elasticsearch, via source code history and JIRA project version, changes made, and error correction data collection (132.1) 10  Testing the collected data through machine learning algorithms The reduction of scenarios (132.2) includes the steps of the process.

8. This is a software testing method compliant with Claim 2, characterized by its use of virtual machines. (150) steps of the process to be realized;  The virtual machine retrieves the project and sections from the database (151), 15  Obtaining test scenarios from the virtual database (152),  Automatic partition creation in the virtual machine (153),  Obtaining coverage data from the virtual database (154),  Obtaining project versions from the virtual database (155),  Automatic 20 via virtual server with virtual database finding scenarios (156),  Obtaining test scenarios from the virtual database (157),  Running the tests involves (158) procedural steps.