[go: up one dir, main page]

WO2018190487A1 - Procédé de visualisation pour l'analyse de traces d'informations de conception de cas d'essai, dispositif de génération de cas d'essai, et support d'enregistrement lisible par un ordinateur - Google Patents

Procédé de visualisation pour l'analyse de traces d'informations de conception de cas d'essai, dispositif de génération de cas d'essai, et support d'enregistrement lisible par un ordinateur Download PDF

Info

Publication number
WO2018190487A1
WO2018190487A1 PCT/KR2017/013459 KR2017013459W WO2018190487A1 WO 2018190487 A1 WO2018190487 A1 WO 2018190487A1 KR 2017013459 W KR2017013459 W KR 2017013459W WO 2018190487 A1 WO2018190487 A1 WO 2018190487A1
Authority
WO
WIPO (PCT)
Prior art keywords
records
nodes
display area
node
displaying
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/KR2017/013459
Other languages
English (en)
Korean (ko)
Inventor
박지환
천선일
김지섭
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Thinkforbl Co ltd
Original Assignee
Thinkforbl Co ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Thinkforbl Co ltd filed Critical Thinkforbl Co ltd
Publication of WO2018190487A1 publication Critical patent/WO2018190487A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/36—Prevention of errors by analysis, debugging or testing of software
    • G06F11/3668—Testing of software
    • G06F11/3672—Test management
    • G06F11/3684—Test management for test design, e.g. generating new test cases
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/36—Prevention of errors by analysis, debugging or testing of software

Definitions

  • the present invention relates to software verification, and more particularly, to a visualization method, a test case generating device, and a computer-readable recording medium for trace analysis of test case design information.
  • Software verification is a universal way of detecting software errors and verifying that software behaves to its requirements. It designes test cases for verification purposes, then executes and measures verification based on the software errors. It is done by tracking and modifying. Test cases are the basis for software verification, and how efficiently you design your test cases determines how quickly you can find many errors.
  • Patent No. 10-1554424 it is difficult to grasp the relationship between the contents described in the technical specification of the software and the nodes in the cause / result table record or the cause / result graph. Validators and others are still struggling to track test case design information to correct errors or modify and change test cases.
  • test case design information that efficiently provides trace analysis of test case design information to a software development maintainer or verifier is needed.
  • Interface is provided.
  • receiving a selection of a first mode or a second mode in the first mode, when one of the plurality of items is selected, at least one record associated with a selected item of the plurality of records and the plurality of items Highlighting at least one node associated with the selected item of nodes; in the first mode, selecting one of the plurality of records, at least one item associated with a selected record of the plurality of items and the plurality of nodes Highlighting at least one node associated with the selected record, and in the first mode, selecting one of the plurality of nodes comprises: selecting at least one item associated with a selected node of the plurality of items and the plurality of records; Highlighting at least one record associated with the selected node further It should.
  • the first display area is selected. Displaying only items associated with the selected item, displaying only records associated with the selected item in the second display area, and displaying only nodes associated with the selected item in the third display area.
  • the document is a functional specification
  • each of the plurality of items is a syntax described in the functional specification
  • the plurality of records is a result of deriving the document using a causal technique
  • the graph is a causal graph to be.
  • a step of receiving a document derives at least one causality table including a plurality of records using a causal technique in the document, and the at least one causality relationship.
  • Deriving a causality graph based on a table, displaying the at least one causality table in a first display area, and displaying the causality graph in a second display area;
  • Each of the plurality of records included in the causality table of the present invention is provided with a graphical user interface (GUI) providing method associated with at least one of the plurality of nodes included in the causality graph.
  • GUI graphical user interface
  • the method when selecting one of the plurality of records and the plurality of nodes, the method further includes displaying only records associated with the selected one in the first display area and displaying only nodes associated with the selected one in the second display area. .
  • selecting one of the plurality of records highlighting at least one node associated with the selected record of the plurality of nodes, and selecting one of the plurality of nodes, selecting the one of the plurality of nodes; Highlighting at least one record associated with the selected node.
  • a test case generating device for automatically generating a test case for determining whether or not a requirement of a specification file of computer software is satisfied, the specification for reading the specification file of the software to be verified.
  • Read / correct An operation controller;
  • a user data input / output unit which provides a graphic user interface (GUI) for interacting with the user and the specification file received from the operation control unit;
  • a database for storing cause / result tables relating to one or more specification files of the software, wherein the operation control unit performs the above-described method to obtain information about the specification file read by the specification reading / correction.
  • a test case generation device is provided that is configured to read information about and store a newly created or updated cause / result table in a database.
  • a computer readable recording medium having recorded thereon a program, the program including instructions, wherein the instructions perform the above-described method when executed by a computer.
  • a trace analysis visualization method and apparatus for test case design information, etc. which can efficiently provide trace analysis of test case design information to a software development maintainer or verifier, can be provided.
  • UX (User eXperience) design development products can minimize the amount of user intervention by automating the creation and validation of test cases, significantly reducing the time and cost of software test case design.
  • Increased test case creation efficiency can be expected by securing additional usability of the item reduction function and the information filtering function.
  • FIG. 1 is a functional block diagram schematically showing the functions of the test case generating apparatus 100 for software verification according to an embodiment of the present invention.
  • FIG. 2A illustrates a main screen of a test case generation method applying a cause & effect test design technique
  • FIG. 2B illustrates a screen structured to execute an essential procedure required to generate a test case of FIG. 2A. It is a figure shown, and step 2c is a figure which shows the flowchart related to this.
  • FIG. 3 is a diagram illustrating FIG. 2A or 2B in more detail. It shows another example of the 'cause, result element list' item.
  • FIG. 4 is a view illustrating FIG. 2A or 2B in more detail.
  • Cause and effect visualization (graph) is enlarged.
  • FIG. 5 is a view illustrating FIG. 2A or 2B in more detail.
  • Test scenario creation ' is an example.
  • FIG. 6 is a view illustrating FIG. 2A or FIG. 2B in more detail. Test data entry.
  • FIG. 7 is a view illustrating FIG. 2A or FIG. 2B in more detail. Test case generation ”.
  • each divided screen may be freely resized and moved.
  • 9A and 9B are diagrams for illustrating the highlighted state according to the present invention.
  • 10A to 10C are diagrams for illustrating an influence grasping state according to the present invention.
  • 'block' or 'unit' refers to a functional part that performs at least one function or operation, and may be implemented in hardware or software or a combination of hardware and software.
  • a plurality of 'blocks' or 'units' may be integrated into at least one software module and implemented as at least one processor, except for 'blocks' or 'units' that need to be implemented with specific hardware. .
  • test case generating apparatus 100 includes a specification reading / correcting unit 102, an operation control unit 104, a user data input / output unit 106, and a database 108.
  • the statement reading / correction unit 102 may read the specification file of the software to be verified from an external or internal memory.
  • the specification file may be a document file in various formats.
  • the specification file may be an open XML format document file having an extension of .docx, .xlsx, or the like, but the present invention is not limited thereto.
  • the specification file is a base specification which describes the structure and operation characteristics of the software to be verified. For example, the writing language, grammar, description of the function of the software, the names of the parameters used, the type and function description, and the error.
  • Various information, including occurrence conditions may be described as sentences or words.
  • Sentences or words included in the specification file include items corresponding to a cause (hereinafter referred to as cause item) related to the function of the software and items corresponding to a result derived from corresponding cause (hereinafter referred to as result item). Can be.
  • the specification file read by the specification read / corrector 102 may be a new specification file or a change specification file.
  • the new specification file is a new specification in which the specification file has not been processed by the test case generating apparatus of the present invention.
  • an item including tag information described below does not exist in the specification file, or It refers to a specification file when a cause / result table related to the specification file does not exist in the database 108.
  • a change specification file is a case where a related specification file has been previously processed by the test case generating apparatus of the present invention and a change has occurred in some items of the specification file since, for example, a tag in the specification file.
  • a description file means that an item including information already exists or a cause / result table related to the specification file already exists in the database 108.
  • the specification file may be read from an internal or external memory (not shown) of the test case generating apparatus 100.
  • the operation control unit 104 may be communicatively connected to the specification reading / correction unit 102, the user data input / output unit 106, and the database 108.
  • the operation control unit 104 may receive information about the specification file read by the statement reading / correction unit 102, output the received information through the user data input / output unit 106, and present the information to the user.
  • the operation controller 104 may also generate or update a cause / result table related to the specification file through interaction with the user through the user data input / output unit 106.
  • the operation control unit 104 may also communicate with the database 108 to determine whether a table related to the read specification file is stored in the database 108, and if there is an associated table, to read information about the table, The newly created or updated cause / result table may be stored in the database 108.
  • the operation controller 104 may also generate a causal graph based on the generated or updated cause / result table, and thereby generate a test case for verifying the corresponding software.
  • the operation controller 104 may output the generated cause / result table, a causal graph, and a test case to the user through the user data input / output unit 106. A detailed operation of the operation control unit 104 will be described later with reference to FIG. 3.
  • the user data input / output unit 106 may include various types of user output devices such as a monitor, a touch screen, various display devices, and the like. According to an embodiment of the present invention, a specification file received from the operation control unit 104, a graphic user interface for interacting with a user, and the like may be displayed to the user through the user output devices of the user data input / output unit 106. have.
  • the user data input / output unit 106 may include various types of user input devices, such as a mouse, a keyboard, a joystick, and various other input devices.
  • the control information input by the user for example, the designation as a cause or effect for each sentence or word of the read specification file
  • Various user control information may be received, including information, user control information about whether or not the specification file changes are reflected.
  • the database 108 may store cause / result tables relating to one or more software specification files.
  • the database 108 may be any type of memory device, although the database 108 is shown as a separate device from the operation control unit 104 in this figure, but the invention is not so limited.
  • the database 108 may be one type of memory structure integrated with the operation control unit 104.
  • FIG. 2A illustrates a main screen of a test case generation method applying a cause & effect test design technique
  • FIG. 2B illustrates a screen structured to execute an essential procedure required to generate a test case of FIG. 2A. It is a figure shown, and step 2c is a figure which shows the flowchart related to this.
  • FIG. 2A and 2B are the same screen, but for the sake of understanding, FIG. 2B shows the roles and functions of the screens separated by dotted lines.
  • the cause and effect items corresponding to the base specification as the base are input to generate the cause and effect table (step 201 of FIG. 2C). This is illustrated by the “2. List of cause and effect elements ”.
  • the meaning of each cause item and the result item may be compared and analyzed, and the items may be reduced and guided according to a user input value after extracting and guiding the items that may be reduced.
  • a causal graph corresponding to the cause and effect table is generated (step 203). This is illustrated by the “3. Cause and Effect Visualization (Graph) ”. According to the graph visualized as described above, verification of cause and effect is facilitated (indicated by "4. Cause and effect verification").
  • Graph causes and effect Visualization
  • the verification of the cause and the result is not easy only due to the visualization in the form of a graph, but is performed by appropriately utilizing the 'emphasis state' and 'effect grasping state' according to the present invention as described below. More preferred.
  • the created causal graph (“3. Cause, Result Visualization”) is converted into a test scenario (step 207). This is illustrated by the “5. Create Test Scenario ”.
  • test data to be used for the test scenario is obtained (step 209).
  • Derivation of this test data may be derived through an operation such as boundary value analysis. This is illustrated in “6. Test data entry ”.
  • a test case generation automation is performed including a process of generating and outputting a test case based on a test scenario (“5. Create a test scenario”) and test data (“6. Test data input”) (step 211). This is illustrated by the “7. Create test case ”item.
  • the highlighted state when an inquiry value is input from a user, information related to the inquiry value is obtained at each execution step, and the information related to the inquiry value is highlighted.
  • the user interface further introduces the concept of distance to quantify the association with other elements, in which the user selects a particular element in a window.
  • the user selects a particular element in a window.
  • FIG. 3 is a diagram illustrating FIG. 2A or 2B in more detail. It shows another example of the 'cause, result element list' item. 3 shows that cause-effect classification is performed. To derive and classify cause and effect from a document (eg, item '1. Requirements' of FIG. 2B).
  • E2 to E5 of FIG. 3 may be regarded as one class and may be marked.
  • FIG. 4 is a view illustrating FIG. 2A or 2B in more detail.
  • Cause and effect visualization (graph) is enlarged.
  • the ophthalmic graph is created, and the causal graph is automatically checked for errors. For example, errors can be displayed in red in the graph area.
  • Hierarchies are expressed to understand element-by-element distances (depth), and annotations can be provided to understand the meaning of the abbreviation. If there are many variables, it can be implemented to enlarge the screen. With respect to FIG. 3, the abbreviated C6 need not be shown in the graph of FIG. 4.
  • FIG. 5 is a view illustrating FIG. 2A or 2B in more detail.
  • Test scenario creation ' is an example.
  • the base scenario is the most influential of the test scenarios.
  • # Indicates the number of the test scenario. For example, in the third test scenario (that is, the base scenario) in the process of passing through C1 to G2, F (false), T (true), T, T, T, F, T, T through the results of E3, E1 It can be seen that.
  • FIG. 6 is a view illustrating FIG. 2A or FIG. 2B in more detail. Test data entry.
  • FIG. 7 is a view illustrating FIG. 2A or FIG. 2B in more detail. Test case generation ”.
  • the uppermost C means checked.
  • the next TC # stands for test case number.
  • test case number 3-1 the expected result in a scenario where input is sequentially caused by F, a valid HTTP identifier, a valid header name, an allocated buffer, the amount of memory allocated to the buffer, and an F is the length of the copied header value.
  • the header value is copied from the HTTP server response.
  • each divided screen may be freely resized and moved.
  • the screen shown in FIG. 2A is illustrated as having a fixed size, but is not limited thereto. Each window may be separated, resized, and moved separately as shown in FIG. 8.
  • 9A and 9B are diagrams for illustrating the highlighted state according to the present invention.
  • FIG. 9A is a screen similar to FIGS. 2A and 2B, in which a document (test specification) appears on the left side, a graph appears on the upper right side, and several tables (four in this example) are shown in other areas.
  • a document including a plurality of items is displayed in the first display area (left side in FIG. 9A), and a document including a plurality of items (function requirements of the test specification) is displayed in the second display area (center in FIG. 9A).
  • At least one table (four tables in FIG. 9A) including a plurality of records is displayed, and a graph including a plurality of nodes is displayed in the third display area (upper right corner in FIG. 9A).
  • each of the plurality of items is associated with at least one of the plurality of records, and each of the plurality of records is implemented with a graphical user interface (GUI) associated with at least one of the plurality of nodes.
  • GUI graphical user interface
  • the document in the first display area is a functional specification
  • each of the plurality of items is a syntax described in the function specification
  • the plurality of records in the second display area are the results of deriving the document using the causal technique.
  • the graph is a causal graph.
  • FIG. 9A illustrates input of a document (function specification), derivation of at least one causality table comprising a plurality of records using a causal technique in the document, and based on at least one causality table.
  • Derive a causality graph display at least one causality table in a given display area (i.e., the center of FIG.
  • Each of the plurality of records included in the at least one causality table may be described as being associated with at least one of the plurality of nodes included in the causality graph.
  • the present invention provides two modes.
  • the first is the emphasis state (highlight mode) described in connection with FIG. 9B.
  • the second is the influence grasp state (impact grasp mode) which will be described later in connection with FIG.
  • the emphasis state (highlight mode) is described first.
  • selecting one of a plurality of items results in at least one record associated with the selected item of the plurality of records (i.e., any record in the plurality of tables in the center) and a plurality of items.
  • Highlights at least one node ie, any node in the graph at the top right associated with the selected item of nodes of. That is, as shown in Figure 9b, when a phrase in the functional specification is selected, the nodes in the records and graphs in the corresponding table are highlighted.
  • the highlight mode if one of the plurality of records is selected, at least one item associated with the selected record among the plurality of items and at least one node associated with the selected record among the plurality of nodes are highlighted. That is, as shown in FIG. 9B, when a record in the table is selected, the phrase in the functional specification and the node in the graph are highlighted.
  • the highlight mode if one of the plurality of nodes is selected, at least one item associated with the selected node of the plurality of items and at least one record associated with the selected node of the plurality of records are highlighted. That is, as shown in FIG. 9B, when a node in the graph is selected, the corresponding text in the function specification and the record in the table are highlighted.
  • the highlighting mode highlights all related items, records, and nodes. This makes it easy to visually identify the association.
  • the function specification is fixed to display the whole (but the highlight state may change), and a predetermined display area (i.e., when one of the plurality of records and the plurality of nodes is selected) is selected. In the center of the drawing, only records associated with the selection may be displayed, and in another predetermined display area, only nodes associated with the selection may be displayed.
  • selecting one of the plurality of records highlights at least one node associated with the selected record among the plurality of nodes
  • selecting one of the plurality of nodes highlights at least one record associated with the selected node among the plurality of records. You may. Also in this case, if necessary, the function specification may be fixed to display the whole (but the highlight state may change).
  • 10A to 10C are diagrams for illustrating an influence grasping state according to the present invention.
  • This configuration is such that only the items in the functional specification of the first display area are selected as necessary. However, the entirety of the basic functional specification may not be viewed, which may be somewhat inconvenient to grasp.
  • the depth value is a positive integer, but conceptually the distance is 0, only the item, the record, and the node will be displayed.
  • the functional specification is the most basic, the functional specification of the first display area (i.e., the left side of the drawing) always appears in its entirety (however, highlights may vary depending on the case), and the second display area (ie, , The record in the center of the drawing and the node in the third display area (that is, the upper right of the drawing) may appear only corresponding to the specific item in the functional specification. This situation is illustrated in FIGS. 10A-10C.
  • FIG. 10A shows an example of a state in which only an element having a distance of 0 from the selected element is displayed in the influence grasping state.
  • FIG. 10B shows an example of a state in which an element having a distance of 1 or less from the selected element is displayed in the influence grasp state.
  • 10C shows an example of a state in which an element having a distance of 2 or less from the selected element is displayed in the influence grasp state.
  • 10A to 10C show an input for a depth value (positive integer), select a particular node from among a plurality of nodes, display only records associated with the particular node in the first display area, and display in the second display area. It displays the nodes that are separated from the specific node by the depth value.
  • a depth value positive integer
  • the above-described method can be written in the form of a program. It may also be embodied in the form of a computer readable recording medium having recorded the program.
  • This program includes instructions that, when executed by a computer, will perform the method described above.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Hardware Design (AREA)
  • Quality & Reliability (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Debugging And Monitoring (AREA)

Abstract

L'invention concerne un procédé de présentation d'une interface d'utilisateur graphique (IUG) à un utilisateur. Les étapes du procédé consistent : à afficher un document incluant une pluralité d'articles dans une première zone d'affichage ; à afficher au moins un tableau incluant une pluralité d'enregistrements dans une deuxième zone d'affichage ; et à afficher un graphique incluant une pluralité de nœuds dans une troisième zone d'affichage. Chaque article de la pluralité d'articles est associé à au moins un enregistrement de la pluralité d'enregistrements, et chaque enregistrement de la pluralité d'enregistrements est associé à au moins un nœud de la pluralité de nœuds.
PCT/KR2017/013459 2016-11-18 2017-11-24 Procédé de visualisation pour l'analyse de traces d'informations de conception de cas d'essai, dispositif de génération de cas d'essai, et support d'enregistrement lisible par un ordinateur Ceased WO2018190487A1 (fr)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
KR20160154262 2016-11-18
KR10-2017-0047759 2017-04-13
KR1020170047759A KR102052338B1 (ko) 2016-11-18 2017-04-13 테스트케이스 설계 정보의 추적 분석을 위한 시각화 방법, 테스트케이스 생성 장치 및 컴퓨터 판독가능 기록매체

Publications (1)

Publication Number Publication Date
WO2018190487A1 true WO2018190487A1 (fr) 2018-10-18

Family

ID=62441347

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2017/013459 Ceased WO2018190487A1 (fr) 2016-11-18 2017-11-24 Procédé de visualisation pour l'analyse de traces d'informations de conception de cas d'essai, dispositif de génération de cas d'essai, et support d'enregistrement lisible par un ordinateur

Country Status (2)

Country Link
KR (1) KR102052338B1 (fr)
WO (1) WO2018190487A1 (fr)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113900958B (zh) * 2021-10-29 2024-12-27 中国电信股份有限公司 测试用例脚本的生成方法、系统、介质及电子设备

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2008181311A (ja) * 2007-01-24 2008-08-07 Toshiba Corp リファクタリング支援装置及びプログラム
US20140189651A1 (en) * 2013-05-21 2014-07-03 Concurix Corporation Animated Highlights in a Graph Representing an Application
KR20150042292A (ko) * 2008-12-02 2015-04-20 아브 이니티오 테크놀로지 엘엘시 데이터 요소 간의 관계의 시각화 및 데이터 요소 속성의 그래픽 표현
KR101554424B1 (ko) * 2014-05-02 2015-09-30 (주)씽크포비엘 테스트 케이스 생성 자동화 방법 및 장치
KR101588027B1 (ko) * 2014-10-10 2016-01-25 (주)씽크포비엘 소프트웨어 현지화를 위한 테스트 케이스 생성 장치 및 방법
US20160217062A1 (en) * 2015-01-23 2016-07-28 Accenture Global Services Limited Test case generation system

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR101629724B1 (ko) 2014-05-27 2016-06-13 한국기계연구원 환자용 이동 보조로봇 및 이를 이용한 환자 이동방법
KR101883027B1 (ko) 2014-12-16 2018-07-27 삼성전기주식회사 유전체 자기 조성물, 유전체 재료 및 이를 포함하는 적층 세라믹 커패시터
KR101675986B1 (ko) 2016-06-13 2016-11-23 (주)씽크포비엘 전장용 소프트웨어 안전성 분석 방법 및 장치

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2008181311A (ja) * 2007-01-24 2008-08-07 Toshiba Corp リファクタリング支援装置及びプログラム
KR20150042292A (ko) * 2008-12-02 2015-04-20 아브 이니티오 테크놀로지 엘엘시 데이터 요소 간의 관계의 시각화 및 데이터 요소 속성의 그래픽 표현
US20140189651A1 (en) * 2013-05-21 2014-07-03 Concurix Corporation Animated Highlights in a Graph Representing an Application
KR101554424B1 (ko) * 2014-05-02 2015-09-30 (주)씽크포비엘 테스트 케이스 생성 자동화 방법 및 장치
KR101588027B1 (ko) * 2014-10-10 2016-01-25 (주)씽크포비엘 소프트웨어 현지화를 위한 테스트 케이스 생성 장치 및 방법
US20160217062A1 (en) * 2015-01-23 2016-07-28 Accenture Global Services Limited Test case generation system

Also Published As

Publication number Publication date
KR102052338B1 (ko) 2019-12-04
KR20180056349A (ko) 2018-05-28

Similar Documents

Publication Publication Date Title
US8850415B2 (en) Generating a transition system for use with model checking
Lin et al. DSMDiff: a differentiation tool for domain-specific models
JP4148527B2 (ja) 機能テスト・スクリプト生成装置
US20190243848A1 (en) Generating a structured document guiding view
US9417991B2 (en) Translation verification testing
WO2018004025A1 (fr) Dispositif de collaboration de documents prenant en charge la correction de style simultanée d'une l'entité et son procédé de fonctionnement
CN109858021B (zh) 业务问题统计方法、装置、计算机设备及其存储介质
CN115904989A (zh) 一种接口测试方法、装置、设备及可读存储介质
US8996357B2 (en) Method for generating diagrams, and information processing apparatus for same
CN110286882B (zh) 一种基于模型检测的前台系统设计与验证方法
CN106407104B (zh) 一种用于检测与内存空间释放相关的缺陷的方法及系统
WO2018190487A1 (fr) Procédé de visualisation pour l'analyse de traces d'informations de conception de cas d'essai, dispositif de génération de cas d'essai, et support d'enregistrement lisible par un ordinateur
US20100095279A1 (en) Method for automatically testing menu items of application software
KR20100069147A (ko) 웹사이트 품질 테스트 방법 및 시스템
WO2022169007A1 (fr) Système de gestion d'interface utilisateur pour outil de configuration d'architecture de système ouvert automobile et procédé associé
JP5576570B2 (ja) 業務仕様からワークフローを生成する方法、プログラム及びシステム
WO2016137035A1 (fr) Dispositif et procédé de génération de cas d'essai, et support d'enregistrement lisible par ordinateur pour enregistrer un programme afin de l'exécuter
JP2014067179A (ja) 文書処理装置及び文書処理プログラム
WO2016085213A1 (fr) Procédé et appareil d'ingénierie inverse de modèle exécutable par ordinateur
TW202139054A (zh) 表單數據檢測方法、電腦裝置及儲存介質
JP2016057715A (ja) 図形式プログラム解析装置
CN115391178A (zh) 基于共享在线文档进行App自动化测试的方法和装置
CN102053909A (zh) 测试程序生成装置
JP4835791B2 (ja) Ｇｕｉ評価システム、ｇｕｉ評価方法およびｇｕｉ評価用プログラム
US12271712B2 (en) Providing metric data for patterns usable in a modeling environment

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 17905798

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 17905798

Country of ref document: EP

Kind code of ref document: A1