KR20130029224A - Apparatus for testing application program automatically based on web - Google Patents

Abstract

According to an embodiment, an apparatus for automatically testing an application developed based on the web may include a document for each stage of development of the application based on information related to the development of the application. A document manager which classifies the document into one of the detailed requirements specification, the design specification, and the source code, and manages the history of the document for each step; And generating a test data required for each stage of the development of the application, and testing the application by using an association between the one step document and a test item corresponding to the one step document. can do.

Description

Device for automatically testing web-based applications {APPARATUS FOR TESTING APPLICATION PROGRAM AUTOMATICALLY BASED ON WEB}

The following embodiments relate to an apparatus for automatically testing an application developed based on the web.

Requirements analysis is the first step in developing software, which is an important step in understanding what needs to be developed. Requirements analysis is the process of understanding the customer's requirements from the developer's point of view and expressing them from the user's point of view so that they can be applied to future development processes. Therefore, there is a need for a method that can systematically handle this process, such as requirements engineering.

Requirements engineering refers to a process that includes all the activities of creating and maintaining requirements documents for the system to be developed. Requirements engineering can consist of process activities such as feasibility studies of systems, derivation and analysis of requirements, specification and documentation of requirements, and verification of requirements.

In requirements engineering, traceability to requirements is important. Traceability refers to the ability to manage the relationship between requirements and other deliverables derived from them. For example, verifying and confirming that artifacts derived from requirements have met and accurately reflected all the features described in the requirements specification are activities that can support the traceability defined above. Deliverables derived from requirements include, for example, various implementations such as design documentation, source code, and executables, and test plans.

Verification is an activity that checks whether the results of the requirements analysis can meet the user's needs and create the right product for the user. In addition, verification is the process of determining whether the output of the current stage matches the output of the previous stage in the development cycle, to ensure that the software is created as the user desires. In order to accurately reflect the functional elements of such requirements, it is necessary to be able to track the functions described in the requirements specification.

According to an embodiment of the present invention, the test output required for the test may be automatically generated by using the information input in the document creation step by establishing an association between the test product and the test product through a web browser. It can provide a device that can.

According to an embodiment, project management for software operating in a distributed environment may be performed through the web to provide convenience to software developers and testers.

According to one embodiment, software is developed through a web browser to provide consistency for the creation of each step document for managing and tracking requirements, while automatically testing each item of the step document to ensure stability and reliability. It can be secured.

According to an embodiment, an apparatus for automatically testing an application developed based on the web may include a document for each stage of development of the application based on information related to the development of the application. A document manager which classifies the document into one of the detailed requirements specification, the design specification, and the source code, and manages the history of the document for each step; And a test manager generating test data required for each stage of development of the application and testing the application by using an association between the one step document and a test item corresponding to the one step document. do.

The project manager may further include a project manager configured to store information related to the development of the application and generate a request query for the output according to the development of the application according to a user's request received through the web browser.

The document manager may further include: a unit item input unit configured to generate a document for at least one unit item of the one step document by using document information for each step of development of the application program input from the user; And an association relationship setter for establishing an association relationship between the at least one unit item using document information for each stage of development of the application program.

Test driver code for automatically generating test cases using test target information including an association between the one step document and the test item, and calling test target functions and interfaces used to perform the test. It may further include a test core for generating a test to execute a test for each step of the development of the application.

According to one embodiment, by providing a common process for creating a document to improve the management of requirements and traceability of requirements during software development, providing a more efficient device for developing software based on components or modules can do.

According to an embodiment of the present disclosure, the interface call relationship between modules can be more easily identified by creating a unit item of each step document according to information input from a software developer and using an association set for tracking the requirements of each unit item. have.

According to an embodiment of the present disclosure, when unit tests and integration tests are performed on the developed software, test drivers and test cases are automatically generated to automate the test execution procedure, thereby making it easy to test the software.

In addition, according to an embodiment, when developing a software based on a component or module, the project can be efficiently managed by a web browser, thereby reducing the cost of software development and testing and shortening the development period.

FIG. 1 is a diagram for describing a process of generating a step document by a document manager in an apparatus for automatically testing an application program developed based on the web, according to an exemplary embodiment.
FIG. 2 is a diagram for describing a relationship between a development document of an application software and a test document for testing and verifying a development document in an apparatus for automatically testing an application program developed based on the web, according to an exemplary embodiment.
3 is a diagram illustrating a data flow according to a process of generating a project for document management in an apparatus for automatically testing an application program developed based on the web, according to an exemplary embodiment.
4 is a diagram illustrating a data flow according to input of unit item information in an apparatus for automatically testing an application program developed based on the web, according to an exemplary embodiment.
5 is a diagram illustrating a process of establishing an association in an apparatus for automatically testing an application program developed based on the web, according to an exemplary embodiment.
6 is a diagram illustrating a test core performed by a test core in an apparatus for automatically testing an application program developed based on the web, according to an exemplary embodiment.
FIG. 7 is a diagram illustrating a data flow when a test project is generated by performing a test in an apparatus for automatically testing an application program developed based on the web, according to an exemplary embodiment.
8 is a diagram illustrating a structure of an apparatus for automatically testing an application program developed based on a web including a document manager and a test manager, according to an exemplary embodiment.
FIG. 9 is a diagram illustrating an association relationship between step documents and an interface call between software modules in an apparatus for automatically testing an application program developed based on the web, according to an exemplary embodiment.
FIG. 10 is a diagram illustrating a structure in which a test driver module is generated as a test project is generated in a test core of an apparatus for automatically testing an application program developed based on the web, according to an embodiment.

Hereinafter, exemplary embodiments will be described in detail with reference to the accompanying drawings. However, the present invention is not limited to or limited by the embodiments. Also, like reference numerals in the drawings denote like elements.

Software testing is primarily aimed at finding and dealing with defects in the system. Software testing also requires the identification and management of current system risks. Depending on the level of software test, the tests that occur at the lowest level are called unit tests or module tests. When testing software, each unit is tested and low-level bugs are found and fixed. Then, they are put together and run integration tests in module groups. This type of testing continues until you can gather more pieces and test the entire product at once, and the integrated test of the entire software is called system testing.

FIG. 1 is a diagram for describing a process of generating a step document by a document manager in an apparatus for automatically testing an application program developed based on the web, according to an exemplary embodiment.

According to an embodiment, an apparatus for automatically testing an application developed based on the web (hereinafter, a test apparatus) includes a project manager 110 and a document manager 150.

The project manager 110 serves to provide a consistent process for creating a document calculated at each stage of development for requirements management of a component or module-based software development project.

More specifically, the project manager 110 stores information related to the development of an application program according to a user's request received through a web browser, and generates a request query for the output according to the development of the application program. Here, the information related to the development of the application may include event information and state information related to the application.

According to an embodiment, the project manager 110 may include a step type input processor 113 and a project generator 115. The step type input processor 113 generates a data structure list based on the step type information on the type of the step document of the project input from the user. The project generator 115 generates a project for generating storage spaces for each step and user of the project.

In addition, the document manager 150, based on the information related to the development of the application, a document for each step of the development of the application request document, requirements specifications, detailed requirements specifications, design specifications and source code of any one Classify documents into steps, and manage the history of documents for each step.

More specifically, the document manager 150 creates a step document for each step of the application development based on the information related to the development of the application, and establishes an association for tracking the requirements for the step document. do. In an embodiment, the establishment of the association relationship makes it easier to determine the selection of components and modules required to satisfy the user's requirements and the interface call relationship between each other. In addition, you can easily track the progress of development through the history tracking of documents created via the Web.

According to an embodiment, the document manager 150 may include a unit item input unit 151, an association relationship setter 153, and a viewer 155.

After creating a project, the unit item input unit 151 generates a project using document information for each stage of development of an application input from a user (for example, unit item information on a unit item including basic and extended elements of the unit item). An XML file for at least one unit item of the step document of each step may be generated.

The affinity setter 153 uses at least one step of project information (e.g., affinity setting information such as information on source items and purpose items specified by the user) of the application input from the user at least in each step of the project. Sets an association between one unit item and stores and manages information about the association.

The viewer 155 shows the result of the document work performed by the unit item input unit 151 and the association setter 153 to the user through a web browser.

In addition, the document manager 150 classifies the step document for each step of the application development into any step document among the step documents shown in [Table 1] below, and records the history of the step document for each step. Can manage

Step documents can include, for example, Request For Proposal (RFP), Software Requirements Specification (SRS), Detailed SRS (DSRS), Software Design Specification (SDS), and Source. Code (Source Code) and the like can be included.

In addition, the test apparatus includes a test manager that performs a test on a required function designed through a combination of respective interfaces and modules, in order to ensure the stability and reliability of the developed components and modules. The test manager will be described with reference to FIG. 7.

FIG. 2 is a diagram for describing a relationship between a development document of an application software and a test document for testing and verifying a development document in an apparatus for automatically testing an application program developed based on the web, according to an exemplary embodiment.

In one embodiment, the type of development document 210 by the project includes a requirements proposal (RFP) 212, a requirements specification (SRS) 214, a detailed requirements specification (DSRS) 216, and a design specification (SDS). 218 and the like.

In addition, the types of test document 250 corresponding to the development document 210 of the software include acceptance test 252, system test 254, integration test 256, and the like. Unit Test 258 may be included.

In one embodiment, the association of unit items given association between the types of steps may be referred to as association setting 230. When the unit items are connected to each other, the unit item in the step located on the left becomes the source item 240, and the unit item located on the right becomes the destination item 245, thereby establishing an association relationship.

The associations between unit items throughout the project are organically linked from the unit item for the user's requirements to the unit item corresponding to the final implementation of the project. In addition, the association applies to each type of test step of test document 250 as well as the type of step of development document 210.

The relationship between the step types (test items) of the test document 250 is closely related to the association between the step types (unit items) of the development document 210.

Thus, if a particular unit item includes a test document 250, the test item 260 in the step type of the test document associated with the specific item while being associated with another unit item in the step type to which the particular unit item belongs. Has an association 220 with.

In this case, the dotted line connecting the correlation 220 between the unit items 240 and 250 of the development document 210 and the test item 260 of the test document 250 may have a relationship of N: M. Indicates. In addition, the unit items of the requirements specification (SRS) 214 may be associated with the test items of the system test 254 and the integration test 256 at the same time.

This association setting 230 allows the user to easily determine whether the software has been implemented through an intermediate design process derived appropriately from the user's requirements, and whether the development has been correctly tested. Can be.

3 is a diagram illustrating a data flow according to a process of generating a project for document management in an apparatus for automatically testing an application program developed based on the web, according to an exemplary embodiment.

The creation of the project begins with a project creation request 325 from the user (hereinafter 'user') 301 of the step document builder. The user 301 inputs information related to the project, such as a project name, a start date and end date of the project, a project participant and a step type, and the like, through an input window of the step document builder when the project is generated (320). Here, the user 301 is assumed to correspond to a user of a manager or higher level of the project.

Upon receiving a project creation request including information related to the project from the user, the project manager 305 registers the information related to the project in the database (330).

The project manager 305 requests the process controller 309 to create a storage space for the project (ie, the main repository) and a user-specific storage space (store) for each of the participants of the project (335).

The process controller 309 controls the operation of the sub version (SVN) 313 which is the external process 311 (340) to generate a storage space (store) (345).

When the result of the creation of the storage space (store) is returned from the process controller 309 (350), the project manager 305 registers the result in the database (DB) (355).

Thereafter, the document manager 307 generates an XML file using information (ie, step type information) about the step (type) (here, the basic step) input by the user 301 (360).

In response to the upload request 365 of the document manager 307, the process controller 309 uploads the document file of the basic step (type) to a storage space (store) of each participant who participated in the project (370).

The document manager 307 receives the upload result of the document file of the basic step (type) from the process controller 309 (375) and stores the result (380).

The viewer 303, which receives the project creation result from the document manager 307 (385), outputs the result (390) and enables the user 301 to check the result (395). This completes the creation of the project.

4 is a diagram illustrating a data flow according to input of unit item information in an apparatus for automatically testing an application program developed based on the web, according to an exemplary embodiment.

The unit item generator 410 receives unit item information from a user (hereinafter, 'user') 401 of the step document creator through the unit item input window 411 and stores basic information about the unit item in a database ( 435,440).

The unit item generator 410 stores the corresponding information (unit item information) in the XML schema (445). At this time, the unit item generator 410 that receives the basic element and the extended element of the unit item through the unit item input window 411 stores the received information in a predetermined structure. The XML processor 415 creates an XML file using the information stored in the structure.

The unit item generator 410 requests the process manager 420 to upload an XML file for the unit item created by the XML processor 415 (450). The process manager 420 controls (455) the operation of the sub-version 417, which is the external processor 430, by the process controller 425 to generate an XML file for the unit item at the time of project creation. Upload to (460).

Thereafter, the upload result returned from the process controller 425 465 is stored 470 in the process manager 420, and then returned 475 to the unit item generator 410 and registered in the database 480. ).

The unit item input window 411 notifies the user 401 of the result of generating the unit item through the viewer 405 (485, 490), and the user 401 confirms the result through the viewer 405 ( 495). Thereafter, when the unit item is modified by the participants of the project, management of the version may be performed by the revision number of the sub version 417.

5 is a diagram illustrating a process of establishing an association in an apparatus for automatically testing an application program developed based on the web, according to an exemplary embodiment.

In FIG. 5, the association setter 510 stores and manages association relationship setting information about association relationships between unit items set by a user (hereinafter, referred to as a 'user') 501 of the step document creator in a database in record form. . When the user 501 deletes the association between the unit items or deletes the unit item, the record inserted in relation to the unit item is deleted from the database.

The association information processor 505 of the association setter 510 that has received the association setting information 515 from the user 501 may request the database controller 507 to store the information about the association (520). ).

In response to the request of 505, the association setter 510 inserts the corresponding information (information about association) into the association table and stores 525, and transmits the processing result to the viewer 503 (530). The user 501 may check the processing result as the result is output 535 through the viewer 503 (540).

6 is a diagram illustrating a test core performed by a test core in an apparatus for automatically testing an application program developed based on the web, according to an exemplary embodiment.

The test core 600 according to an embodiment is a module for automatically performing a test in connection with a document manager, and automatically generates a test case using test target information including an association between a step document and a test item. You can generate test driver code to call the functions and interfaces under test that are used to perform the tests. The test core 600 may execute a test for each stage of development of the application by using the generated test case and test driver code.

The test core 600 includes a test target information collector 610, a test case generator 620, a test driver generator 630, a test executor 640, a test result analyzer 650, a unit item tester viewer 660, and components. Platform 670 may be included.

The test object information collector 610 collects test object information including an association relationship between the test item and at least one unit item from the document manager.

The test case generator 620 receives test object information 135 and test case candidate value generation conditions from a user and automatically generates a test case.

The test driver generator 630 generates test driver code for calling a test target function and an interface used to perform a test.

The test executor 640 executes a test on a result calculated at each development stage of the project by using test driver code. The test executor 640 may be divided into a unit test executor 641 and an integrated test executor 645.

The unit test executor 641 may test the interface information collected from the unit item of the step document input from the user and the information about the code item related to the interface information.

In addition, the integration test executor 645 tests the interoperability between the source code and at least one module for the project using the association between the function's interface and the higher level document related to the functionality required in the higher level document of the step document. can do. The integrated test runner 645 may include a platform controller for controlling the component platform 670 and additional environmental configuration information required for the test.

The test subject information collector 610 may perform the test through the test manager by using the correlation between the document item and the test item of FIG. 2, by using the test target information collector 610. By collecting.

In order to perform unit tests of components and modules, the test core 600 may collect interface information from the requirements specification (SDS) and collect and test information of code items related thereto.

In addition, the test core 600 may perform the test by using the correlation between the step requirement document that sets the unit request function information from the detailed requirements specification (DSRS) and related functions and codes for the integrated test. .

When the test target information is collected, the test core 600 automatically generates a test case, a test driver, and performs a test, and the test result is notified to the user. The user can check the test result by the document manager or the test manager.

The integration test performed by the integration test executor 645 is a test for a function in which several modules and source codes interoperate with each other, and thus may include a function for performing an operation of a request platform for operating a target function internally. .

FIG. 7 is a diagram illustrating a data flow when a test project is generated by performing a test in an apparatus for automatically testing an application program developed based on the web, according to an exemplary embodiment.

Performing testing and verification of the software can be performed using the association between the document management phase and the test phase. The association of test items is established by creating a test project.

The user of the unit item tester (hereinafter, the test manager 705 having received the test request 720 from the user 701) requests the test core 710 to generate a test project (725).

Here, the test project is a test project for detailed items of the step type in the document management process, and a 1: N relationship may be established between the development project and the test project. That is, several test projects may be generated for the detailed items of the step type.

The test manager 705 automatically executes a test including generating a test driver, adding a test interface, and generating a test case to test the function of each developed component and application software in which the components are combined. This test automation makes it possible to efficiently test software designed on a component or module basis by using the correlation between development information inputted through the step writer and document information and documents.

The test manager 705 registers the information of the test project in the database and establishes an association between the development process and the test process (or the development document and the test document) by using the association setting information of the item set by the document manager.

In addition, the test manager 705 generates the necessary test data for each stage of the development of the application, and the association between the test document corresponding to any one of the step documents and the step document of the step documents shown in [Table 1] Test the application using relationships.

In this case, the test case generator 713 may generate a test case based on the set relation. In addition, the established association enables the project manager to easily check whether the test for the document unit item is performed correctly after performing the test.

In FIG. 7, the test core 710 automatically generates a test case using test target information including an association between a step document and a test item, and calls a test target function and interface used to perform a test. You can generate test driver code to run tests for each stage of your application development.

To this end, the test information collector 711 of the test core 710 that receives the request for generating a test project from the test manager 705 includes test object information including an association relationship between the test item and at least one unit item in the step document. Can be collected (730). The test information collector 711 requests the test case generator 713 to generate a test case (735).

In response to the request of 735, the test case generator 713 automatically generates a test case used for testing the step document by using the test target information and the candidate value generation condition for the test (740). Thereafter, the test case generator 713 requests the test driver generator 715 to generate a test driver (745). In response to the request of 745, the test driver generator 715 generates a test driver 750 and then informs the viewer 703 that the test preparation is completed through the viewer 703. As such, when the user selects a test method, the test core 710 may automatically generate a test case and a test driver by using the set correlation.

When generation of test cases and test drivers is complete, test manager 705 notifies the project manager that it is ready for test execution. At this time, all procedures of the test are performed by the test core 710, and after the test is completed, the test result receiver, which is an internal module of the test manager 705, is notified that the test is completed and informs the user of the result.

The user 701 requests the test executor 717 to execute the test as the test preparation is completed (760).

The test executor 717 performs a test by the test case and the test driver generated earlier, and stores the result (765). According to the analysis request 770 of the test result of the test executor 717, the test result analyzer 719 analyzes 775 the test result and passes the result to the test manager 705 (780).

In this case, the test result is output through the screen (785), the test manager 705 stores the received test result in the database (790).

The test manager 705 outputs the result 795 through the viewer 703 to allow the user 701 to check the test analysis result (797).

8 is a diagram illustrating a structure of an apparatus for automatically testing an application program developed based on a web including a document manager and a test manager, according to an exemplary embodiment.

According to an embodiment, an apparatus for automatically testing an application developed based on the web (hereinafter, referred to as a “test apparatus”) 800 may be configured by establishing a relationship between a development product (eg, a step document) and a test item. Management of documentation generated by development, collaboration among project participants, and automated testing of development results can effectively validate software stability and reliability.

In order to support this, the test apparatus 800 includes a client client (Seed Client) 810 composed of a web service module accessed through a web browser 860 and a server (SEED Server) for performing project management for multilateral cooperation. 820, a test core 830, and an external application process 840 for testing and verifying the developed software.

Client portion 810 may include web service modules that are accessed through web browser 860.

The client portion 810 is a client service 861 that directly receives a user's request, transitions 862 according to the type of the user's request, and a project manager 863 that performs project management in the client portion 810. It includes.

The server 820 manages step documents calculated for each development step of a project for developing software according to a user's request received through the web browser 860, and includes at least one unit item and at least one unit of the step document. Collect test target information based on the correlation between test items corresponding to the items.

The server 820 includes a project manager 821, a document manager 822, a configuration manager 833, a test manager 824, and an issue manager. 825 and an event notifier 826.

In addition, the server 820 may process a request received from the client portion 810 connected to the TCP / IP 850 and transmit the processing result to the client portion 810.

Project manager 821 receives a request for current project information from client portion 810, and processes and stores the data received from client portion 810. The project manager 821 stores event information and state information related to the project, and may generate an overall request query regarding sub-items (eg, unit items or test items) of the project.

The project manager 821 may store information related to the development of the application and generate a request query for the output according to the development of the application according to a user's request received through the web browser.

In addition, the project manager 821 may query and process data received from the database 841 or the configuration manager 823, and transmit and receive information to the client portion 810.

Based on the information related to the development of the application, the document manager 822 creates a step document for each step of the development of the application, and establishes an association relationship for tracking the requirements for the step document.

The document manager 822 may manage stage documents calculated for each stage of development of the project. The document manager 822 calculates stage documents calculated for each stage of development of the project, that is, five documents such as [Table 1] described above as outputs for each stage of development. Can support templates Document templates include, for example, Request For Proposal (RFP), Software Requirements Specification (SRS), Detailed SRS (DSRS), Software Design Specification (SDS), and Source. Code (Source Code) and the like can be included.

The configuration manager 823 supports integrated version management of the documents (ie development documents) and source code developed through the project. The configuration manager 823 works in conjunction with the existing version control tool Subversion 842 to create a storage space for the user, and to perform subversions such as commit, checkout, and update. Automatically perform the functions of the configuration to support configuration management without additional user interaction.

The test manager 824 generates necessary test data for each stage of the development of the application, and tests the application using an association between the step document and the test items corresponding to the step document.

To this end, the test manager 824 generates necessary test data (or test cases and test drivers) in at least one unit item of the step document. In addition, the test manager 824 sets an association relationship between the at least one unit item and the at least one test item corresponding to the at least one unit item.

In this way, the user may check the linkage between the at least one unit item of the step document and the test item required in the at least one unit item, and check the test result received from the test core 830.

The test manager 824 may further include an event notifier 826 for being notified of the test result by the test core 830.

The test core 830 automatically generates test data for the project based on the test target information, and uses the test data to execute a test on the result calculated at each stage of the project development. Here, the meaning of 'generating test data automatically' may be used to mean generating a test case and generating a test driver.

The external application process 840 includes a database 841 for storing project and XML 843 document information and a version control controller (Subversion) 842 for shape management. In this case, the version control controller 842 may use another version control tool.

FIG. 9 is a diagram illustrating an association relationship between step documents and an interface call between software modules in an apparatus for automatically testing an application program developed based on the web, according to an exemplary embodiment.

Devices that automatically test web-developed applications (hereafter referred to as "test devices") are required to complete the unit-level (e.g., source and destination) sections of the document before and after the completion of each unit item. Set an association. Accordingly, the test apparatus may derive the call relation between the module and the interface necessary to satisfy the user's requirement using the association relation.

The test apparatus inputs the detailed requirements of the application software to be developed as a unit item of the detailed requirements specification (DSRS) among the step documents, and inputs components and interfaces necessary for implementing the function as the unit item of the design specification (SDS).

In addition, the test device can use the associations between these (in this case, unit items) to verify the interface relationships between the modules needed to meet the requirements of the software. In this case, the type of the module and the interface may be designed using an association relationship between the unit items, and the call direction of the interface may be designed using the upper and lower relationships of the unit items.

FIG. 10 is a diagram illustrating a structure in which a test driver module is generated as a test project is generated in a test core of an apparatus for automatically testing an application program developed based on the web, according to an embodiment.

The test driver generator automatically generates a test driver module after collecting information about the application software to be tested by the test information collector. Here, the test driver module refers to a module having a request interface for a software module to be tested, so that the test core can perform a test by calling the request interface.

For the integrated test, the test core (or more precisely, the test driver generator) adds a test driver module by adding a runTest interface 1010 for testing using the association between the document item and the test item in the connection structure of the existing module shown in ② of FIG. 9. (MoveObject TestDriver Comp) 1030 may be created. The user may write an algorithm to test inside the runTest interface 1010 to automatically perform a functional test on the combined module.

The method according to an embodiment of the present invention can be implemented in the form of a program command which can be executed through various computer means and recorded in a computer-readable medium. The computer readable medium may include program instructions, data files, data structures, etc. alone or in combination. The program instructions recorded on the medium may be those specially designed and constructed for the present invention or may be available to those skilled in the art of computer software. Examples of computer-readable media include magnetic media such as hard disks, floppy disks and magnetic tape; optical media such as CD-ROMs and DVDs; magnetic media such as floppy disks; Magneto-optical media, and hardware devices specifically configured to store and execute program instructions such as ROM, RAM, flash memory, and the like. Examples of program instructions include machine language code such as those produced by a compiler, as well as high-level language code that can be executed by a computer using an interpreter or the like. The hardware devices described above may be configured to operate as one or more software modules to perform the operations of the present invention, and vice versa.

As described above, the present invention has been described by way of limited embodiments and drawings, but the present invention is not limited to the above embodiments, and those skilled in the art to which the present invention pertains various modifications and variations from such descriptions. This is possible.

Therefore, the scope of the present invention should not be construed as being limited to the embodiments described, but should be determined by equivalents to the appended claims, as well as the appended claims.

110: project manager
113: Step type input handler
115: project generator
150: document manager
151: unit item input method
153: Association Setter
155: viewer

Claims (4)

Based on the information related to the development of the application, the document for each stage of the development of the application is classified into a stage document of any one of a request proposal, a requirements specification, a detailed requirements specification, a design specification, and source code, A document manager for managing a history of documents for each step; And
A test manager which generates necessary test data for each stage of development of the application and tests the application by using an association between the one step document and a test item corresponding to the one step document.
Apparatus for automatically testing the application developed based on the web. The method of claim 1,
The project manager stores information related to the development of the application and generates a request query for the output according to the development of the application according to a user's request received through a web browser.
Apparatus for automatically testing the application developed based on the web further comprising. The method of claim 1,
The document manager
A unit item input unit configured to generate a document for at least one unit item of the one step document by using document information for each step of development of the application program input from the user; And
An association relationship setter for establishing an association relationship between the at least one unit item using document information for each stage of development of the application program
Apparatus for automatically testing the application developed based on the web. The method of claim 1,
Test driver code for automatically generating a test case using test target information including an association between the one step document and the test item, and calling a test target function and interface used to perform the test. Create a test core to run a test for each stage of development of the application
Apparatus for automatically testing the application developed based on the web further comprising.

Images