CN110244934B - Method and device for generating product demand document and test information - Google Patents

Method and device for generating product demand document and test information Download PDF

Info

Publication number
CN110244934B
CN110244934B CN201810217550.7A CN201810217550A CN110244934B CN 110244934 B CN110244934 B CN 110244934B CN 201810217550 A CN201810217550 A CN 201810217550A CN 110244934 B CN110244934 B CN 110244934B
Authority
CN
China
Prior art keywords
component
product
configuration
information
test
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.)
Active
Application number
CN201810217550.7A
Other languages
Chinese (zh)
Other versions
CN110244934A (en
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.)
Alibaba Group Holding Ltd
Original Assignee
Alibaba Group Holding 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 Alibaba Group Holding Ltd filed Critical Alibaba Group Holding Ltd
Priority to CN201810217550.7A priority Critical patent/CN110244934B/en
Publication of CN110244934A publication Critical patent/CN110244934A/en
Application granted granted Critical
Publication of CN110244934B publication Critical patent/CN110244934B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/10Requirements analysis; Specification techniques
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/36Preventing errors by testing or debugging software
    • G06F11/3668Software testing
    • G06F11/3672Test management
    • G06F11/3684Test management for test design, e.g. generating new test cases
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/36Preventing errors by testing or debugging software
    • G06F11/3668Software testing
    • G06F11/3672Test management
    • G06F11/3688Test management for test execution, e.g. scheduling of test suites
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02PCLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
    • Y02P90/00Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
    • Y02P90/30Computing systems specially adapted for manufacturing

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Hardware Design (AREA)
  • Quality & Reliability (AREA)
  • Software Systems (AREA)
  • User Interface Of Digital Computer (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

The embodiment of the application discloses a method and a device for generating a product demand document and test information, wherein the method comprises the following steps: providing an operational option for configuring product requirements; receiving product demand configuration information through the operation options, wherein the configuration information comprises a product demand document template, a component set and a service rule set under each component required by a product; and generating a product demand document according to the configuration information. According to the embodiment of the application, the research and development time can be shortened, the efficiency is improved, the product development document can be effectively precipitated, and the data resource utilization rate is improved.

Description

Method and device for generating product demand document and test information
Technical Field
The application relates to the technical field of product development, in particular to a method and a device for generating a product demand document and test information.
Background
When a software product is developed, one software product relates to a plurality of product functions, different product managers need to develop specific product functions to generate product demand documents, and when the product managers generate the product demand documents, the product managers completely rely on own knowledge of the products and own unique text writing habits to manually write and generate the product demand documents, so that testers can perform further software product development processing according to the product demand documents.
In the actual development process, because enterprise personnel mobility is great, when new product manager carries out secondary development to the product, just need read and understand former product demand document, do secondary development on this basis again, because every people's thinking mode is different, write the custom also different, therefore, this kind of mode that relies on the personal understanding ability purely has greatly restricted product development efficiency.
In addition, because the products of the same enterprise have a certain technical relevance, different product managers need to communicate with each other to know the functional requirements of the products, and then the products can be researched and developed to generate a qualified product requirement document, and the way of purely relying on personal language communication capability also limits the product development efficiency to a certain extent.
Disclosure of Invention
In order to solve the technical problems, the embodiment of the application provides a method and a device for generating a product demand document and test information, which can realize standardized product demand documents, and further automatically generate test cases or test scripts on the basis of the documents.
Therefore, the embodiment of the application provides the following technical scheme:
a method of generating a product demand document, comprising:
providing an operational option for configuring product requirements;
Receiving product demand configuration information through the operation options, wherein the configuration information comprises a product demand document template, a component set and a service rule set under each component required by a product;
and generating a product demand document according to the configuration information.
A method for generating product test information comprises the following steps:
providing an operational option for configuring product requirements;
receiving configuration information of product requirements through the operation options, wherein the configuration information comprises a component set required by the product and a service rule set under each component;
and generating a test case for carrying out product test according to the configuration information and the pre-obtained topological relation information between the services.
A product demand document generation apparatus comprising:
an operation option providing unit for providing operation options for configuring product requirements;
the configuration information receiving unit is used for receiving product demand configuration information through the operation options, wherein the configuration information comprises a product demand document template, a component set and a service rule set under each component required by a product;
and the demand document generation unit is used for generating a product demand document according to the configuration information.
A product test information generating apparatus comprising:
an operation option providing unit for providing operation options for configuring product requirements;
the configuration information receiving unit is used for receiving the configuration information of the product requirement through the operation options, wherein the configuration information comprises a component set required by the product and a service rule set under each component;
and the test case generating unit is used for generating a test case for carrying out product test according to the configuration information and the pre-obtained topological relation information among the services.
A computer system, comprising:
one or more processors; and
a memory associated with the one or more processors, the memory for storing program instructions that, when read for execution by the one or more processors, perform the operations of:
providing an operational option for configuring product requirements;
receiving product demand configuration information through the operation options, wherein the configuration information comprises a product demand document template, a component set and a service rule set under each component required by a product;
and generating a product demand document according to the configuration information.
A computer system, comprising:
one or more processors; and
a memory associated with the one or more processors, the memory for storing program instructions that, when read for execution by the one or more processors, perform the operations of:
providing an operational option for configuring product requirements;
receiving product demand configuration information through the operation options, wherein the configuration information comprises a product demand document template, a component set and a service rule set under each component required by a product;
and generating a test case for carrying out product test according to the configuration information and the pre-obtained topological relation information between the services.
Compared with the prior art, the embodiment of the application has the following advantages:
according to the implementation scheme, the product demand document can be automatically generated by configuring the document model, the component set and the service rule set required by the product, so that standardization and standardization of the product demand document can be realized, meanwhile, the research and development time can be shortened, the efficiency can be improved, the product development document can be effectively precipitated, and the data resource utilization rate can be improved.
In addition, because the configuration information of the specific product can be recorded, including specific components, business rules and the like, the test case can be automatically generated for the specific business rules by pre-storing the business topological relation information in the product, so that the test efficiency is also improved.
Furthermore, because the structural expression of the business rules can be realized, and the structural expression comprises the characteristic value information corresponding to the business rules, the test data can be automatically screened out from the real business data on the basis of realizing the test cases, the test script is generated, and the research and development efficiency is further improved.
Of course, not all of the above-described advantages need be achieved at the same time in practicing any one of the products of the present application.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings that are required to be used in the embodiments or the description of the prior art will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments described in the present application, and other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
Fig. 1 is a diagram illustrating a scenario in practical application of the present application;
FIG. 2 is a flow chart of a first method provided in an embodiment of the present application;
FIGS. 3-1 to 3-4 are schematic diagrams of configuration interfaces provided by embodiments of the present application;
FIG. 4 is a flow chart of a second method provided by an embodiment of the present application;
FIG. 5 is a schematic diagram of a first apparatus according to an embodiment of the present disclosure;
FIG. 6 is a schematic diagram of a second apparatus according to an embodiment of the present disclosure;
fig. 7 is a schematic diagram of a computer system according to an embodiment of the present application.
Detailed Description
In order to better understand the technical solutions in the present application, the following description will clearly and completely describe the technical solutions in the embodiments of the present application with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only some embodiments of the present application, not all embodiments. All other embodiments, which can be made by one of ordinary skill in the art based on the embodiments herein without making any inventive effort, shall fall within the scope of the present application.
For ease of understanding, the product-related concepts will first be described below. In embodiments of the present application, a product may generally refer to a plurality of pages, a plurality of components may be associated in a page, and a plurality of business rules may be included in a component.
For example, for the "world cat international" product, the pages involved may include detail pages, order pages, etc., and the order pages may include "ship-to address component," "coupon component," etc. Wherein, a component can be regarded as a set of interrelated business rules, which are page elements generated by aggregating functions of the interrelated business rules; components may generally include component display instance diagrams, component introductions, and business rules. For example, taking an invoice component as an example, the invoice component can contain a plurality of business rules, such as making an order of fresh commodities to support making an electronic invoice, but not support making a paper invoice, selecting whether to make an invoice or not on a book commodity order page, and forcedly making an invoice on an electric appliance commodity order page; for another example, aggregating and generalizing business rules associated with the shipping address module into a "shipping address" component, e.g., in the "triage" order page, the "shipping address" component may contain a number of business rules, e.g.: 1. if the buyer does not store the receiving address, the ordering page guides the buyer to perfect the receiving address information; 2. the receiving address module in the order page allows to store at most 20 receiving address information and other business rules; in the embodiment of the application, the business rule of the page logic and the bottom logic related to the receiving address module is generalized and defined as a receiving address component.
Based on the above analysis, in the development platform provided in the embodiment of the present application, a function for generating a Product Requirement Document (PRD) by a configuration manner may be provided for a product manager (PD) user, through which a configuration interface may be provided for the user, the PD may configure a page related to the product, a required component, a business rule in the component, and the like through the configuration interface, and may further provide a document template, and the PD may automatically generate the PRD document by configuring the above information and selecting a specific template. The PRD document generated in this way has the characteristics of standardization. In addition, because the specific information such as the component information and the business rule can be stored in the form of configuration information, test information such as test cases or test scripts can be automatically generated on the basis of the configuration information, and the related test personnel are not required to manually generate the test cases or the test scripts by reading the PRD document.
In addition, in order to better support automatic generation of test information, in the preferred embodiment of the application, the business rule may be defined in a structured form. For example, a specific business rule may include: characteristic value, operation steps and expected result. For example, a business rule, the natural language of which is expressed as "whether a user of a page in a book commodity of a book website invoices" is structured, and the corresponding structured expression language includes: the feature value in the precondition is book commodity, the operation steps are user ordering, the expected result is whether the invoice option can select to issue invoice, and the like. In this way, for a business rule, specific test data can be generated from the full-link functional platform according to the definition of the characteristic value, and a test script can be generated according to the information such as the topological relation diagram among preset businesses. The test script may be an execution code generated according to a specific operation step, and then, the test script is executed through the test platform, which is equivalent to executing an operation step included in the service rule, and comparing the script execution result with the expected result, so as to determine whether the test is passed.
The following description describes the implementation of the present application in connection with the actual application scenario.
Referring to fig. 1, fig. 1 is an exemplary diagram of a scenario in practical application, as shown in fig. 1, a method for generating a product requirement document provided by the present application is applied to a terminal and a server in a form of a client and a server, as shown in fig. 1, in a terminal 101 and a server 102, the terminal 101 and the server 102 are in communication with each other to provide a development platform for a developer, so that the developer of the product requirement document develops based on a unified and standardized development platform, thereby effectively precipitating the product requirement document and improving the utilization rate of data resources. As shown in fig. 1, a PD user a accesses a server 102 by using a terminal 101, the terminal 101 may provide a configuration interface for the PD user, send configuration information input by the user on the configuration interface to the server 102, and the server 102 generates a PRD document according to a PRD document template selected by the user and the configuration information input by the user. The server 102 may then save the PRD document, and may additionally send the PRD document to the terminal 101, where the terminal 101 displays the product demand document to the PD user a. It should be noted that, the server 102 may provide the service of automatically generating the product demand document for the terminals of a plurality of PD users through the network.
In addition, the server 102 may store the designed product requirement document, so that other PD users or testers may view the designed product requirement document, as shown in fig. 1, the PD user B may view the product requirement document through network communication between the terminal 103 and the server 102, so that the product requirement document can be quickly known, and product upgrading is convenient. It should be noted that, the server 102 may provide the product requirement document query service for the terminals of multiple PD users through the network, and process the query process of multiple product requirement documents synchronously and in parallel.
Here, the terminal 101 may be a terminal device such as a desktop computer, a notebook computer, a tablet, or the like; terminal 103 is similar to terminal 101; the server 102 is a device for providing data services, such as a web server, an APP server, etc., and in practical application, may be an independently deployed server device, or may be a server deployed by a cluster.
Based on the above application scenario, the following describes in detail a specific implementation scheme provided in the embodiment of the present application.
Example 1
The first embodiment of the present application provides a method for generating a product requirement document, referring to fig. 2, the method specifically may include:
S201, providing operation options for configuring product requirements; the method comprises the steps of carrying out a first treatment on the surface of the
In the embodiment of the application, a standardized development platform can be provided for the PD user through a network framework of a server-client or a server-browser, and the PD user can generate a product demand document by utilizing the client to communicate through a network.
Specifically, when the PD user needs to develop the product requirement document, the client configured in the terminal may be started, for example, click on the client, or log in the website of the configuration interface through the browser, the developer performs these operations, and when the client monitors that the PD user performs these operations, the client sends a rendering request of the configuration interface to the server.
After receiving a rendering request about a product demand document configuration interface sent by a client, a server can feed back interface data of the configuration interface to the client, wherein the interface data refers to data capable of generating the configuration interface through rendering; for the server side, data support can be provided for a plurality of clients through network communication, and when the server side receives a plurality of rendering requests at the same time, the server side can initiate a plurality of processes to feed back interface data to the clients in parallel.
Specifically, in order to provide a standardized configuration interface, the embodiment of the application proposes a layered configuration mode based on the actual requirement of product development, and the layered configuration mode is more specifically presented in a layered configuration interface; wherein the primary hierarchical logic may be determined based on relationships between elements in the product as previously described. For example, since a product includes at least one page, a page includes at least one component, and a component includes at least one business rule; based on this, it is further proposed that the hierarchical configuration interface comprises: different configuration interfaces are constructed according to the hierarchical relationship among the four parts of the product, the page, the component and the business rule.
More specifically, the configuration interface includes: the method comprises the steps that a first layer of configuration interface is generated according to a product configuration control, and the first layer of configuration interface is used for bearing the configuration control for configuring basic information of a product;
the second layer configuration interface is generated according to the page configuration control, and is used for bearing the configuration control for configuring the page related information;
a third layer of configuration interface generated according to the component configuration control is used for bearing the configuration control for configuring the related information of the component; the components are generated according to business rules. Wherein the components are generated according to business rules.
The interface data fed back by the server to the client specifically includes: interface data of the first layer configuration interface, interface data of the second layer configuration interface, interface data of the third layer configuration interface, and interface data of the fourth layer configuration interface.
It should be noted that, in the process of developing a PRD document specifically, the interfaces of the layers may not all be needed, but the configuration interfaces of which layers are used may be determined according to the needs of the specific situation.
S202: receiving product demand configuration information through the operation options, wherein the configuration information comprises a product demand document template, a component set and a service rule set under each component required by a product;
in particular implementations, there may be multiple ways in which the PD user initiates generation of the PRD document. For example, in one approach, since the server may store specific product information after each generation of the PRD document, the product information includes the specific PRD document, as well as associated component set information, test cases, test scripts, and so forth. While the subsequent product may continue to be developed based on the previous product or may be very strongly associated with the previous product, the PD user of the current product may be customized based on the relevant configuration information of the existing product. Alternatively, an entirely new product may be customized, i.e., the association of the current product with the previous product may not be large, and thus the entirely new product may be customized.
Wherein, for the first mode, an operation option for selecting from the existing products can be provided, the selected target existing product information is received through the operation option, the configuration information related to the target existing product is provided, and the operation option for editing on the basis of the configuration information related to the target existing product is provided, so that the configuration information of the current product is determined by the mode of editing on the basis of the configuration information related to the target existing product. For example, in a specific implementation, optional product labels may be displayed for the PD user in the first layer configuration interface, where the optional product labels may include products that are developed by the current PD user, or products that are developed by other PD users, and in the specific implementation, two directories, i.e., my product and all product, may be distinguished, so that the current PD user may select. After a specific product label is selected, the PRD document template corresponding to the existing product can be used as the PRD document template selected by the current product, and in addition, the component set information corresponding to the existing product can be displayed in a third layer of configuration interface. In this way, the PD user can continue customization based on the existing product-associated component set, including adding new components, re-customizing business rules for existing components, and so forth, to generate a component tree for the current product. In the process of adding a new component or customizing an existing component, operations such as editing or inputting business rules can be realized through a fourth layer configuration interface.
For the second way, since the product is completely new to be customized, an operation option for completely customizing the product, and optionally a product requirement document template and page information can be provided, and then the selected target product requirement document template, and the related target page can be received through the operation option. Further, a set of base component information associated with the target page and operation options for editing the base component may be provided to determine a set of components and a set of business rules for the current product by editing the base component information associated with the target page. For example, in a specific implementation, after receiving a request of a current PD user, an interface for configuring a product name, a document structure block included in a PRD document, or the like may be provided, where the document structure block may be expressed in a tree structure, and may support a multi-level tree structure. For example, a primary node may include an overview and a function, a secondary node under the overview node may also include a secondary node for context, goal, plan, risk, etc., a secondary node under the function node may also include a summary of the function, details of the need, etc., and so on. By customizing the document block, a new PRD document template can be generated, and the template is used for generating the PRD document by default in the current development process.
In addition, optional page information can be provided through a second layer configuration interface, and the PD user selects a target page through the second layer configuration interface according to the page related to the product required to be developed. After the target page is selected, the basic component set associated with the target page can be displayed through a third layer of configuration interface. Furthermore, the PD user may select a component in the third layer configuration interface, or may add a new component through the third layer configuration interface when a new component is required to be used; customization of the existing base component may also be initiated through the third configuration interface, and so on, when customization of the base component is desired. And then, inputting or editing specific business rules in the component through a fourth layer configuration interface.
That is, either the first or second mode described above, an operation option for performing component set editing may be provided, and further, a component tree may be generated from the component set editing result; wherein, the operation options for editing the component set may include: operational options for selecting from known components, for adding operational options for new components, and for customizing the original components, etc. For example, in the specific implementation, in the third layer configuration interface, the component selected by the PD user may be displayed in the form of a component tree, and such component tree supports new additions and modifications, and is stored in the document template information after being saved. When clicking the service component tree node, the basic information of the page is displayed, which mainly comprises the pre-information of the page (used for identifying the current page access condition and the system operation provided by the page, the system operation can be transmitted to each component operation), and meanwhile, the current page component information is displayed according to the rule. If the customization is brand new, all basic component names, component details and other service components of the current page are displayed by default, and click expansion is supported. If the product is an original product upgrade, the default display product customizes the component name, the component details and other components, and click display is supported.
The components have two classification dimensions, the first is aggregated according to functions and is mainly used for maintaining the association logic of the components; the second type is mainly used for maintaining page UI position identification, and can be customized by each page, for example, the following single pages can be divided into: commodity blocks, store blocks, parcel blocks, global, system level, etc., the block classifications are directly displayed on the user demand customization page.
When a component (when the requirement is prior to code development) which is not existed in the newly added system is required, the operation of the component, the check points and the like can be unknown, and at the moment, the operation and check point logic model can be extracted for identifying when the new system is added. For example, the configuration interface of a specific newly added component may be as shown in fig. 3-1, where the component name may be customized by the PD user, and the length of the name, the character type, and the like may be limited, for example, limited to 10 characters or less, and no special character is supported. In addition, component names may also be mapped with code in the test platform components. With respect to component introduction information, user input may be supported for introducing component primary services and current online status, as well as other information requiring remarks. The pre-information is a primary node of a basic feature, for example, for a product in a certain network sales platform, the basic feature can be divided into: buyers, sellers, commodities, orders, etc., for regular configuration time-setting scenarios. The test platform provides option selection, which is only used for identifying operation, and after the code function is online, the actual action can be configured on the corresponding option. Business rules fall into two categories: the components are related, wherein the association component is used for identifying the change range estimation, and whether the association influence is established or not is finally determined by a user.
When the original components are required to be customized, the platform realizes the business components, and the component customization is finished in the initial product, but the business rules are required to be changed in the current product. In this regard, component details may be expanded by clicking on the component name in the third tier configuration interface, where each component may be divided into component introduction, component prepositions, component operations, business rules (component business rules, association business rules), association components. In order to avoid affecting other existing products, the original business rules may be required to be unchanged, and only new rules are supported and existing rules are deleted. After the customization is completed, the component version and the component snapshot can be saved, and setting information and component difference display when the product references the component can also be recorded. In addition, when the component version in the product is changed, the user can be prompted to change the component, and the change details including new and old component configuration information and the product to which the new and old component configuration information belongs are supported to be checked.
Whether the component is newly added or the business rule is newly added in the original component, the business rule can be specifically added in the fourth layer configuration interface. The new rule interface can support switching different modes, such as a natural language template and an expressive language template, and takes a daily cat supermarket commodity detail page freight rate display as an example, and the natural language is: the freight of the commodity detail page of the cat supermarket is displayed as 'full 88-yuan package mail'; the expression language is the precondition: commercial product-Tianmao supermarket, operation steps: rendering commodity details, and expecting results: the freight module presents a "full 88-membered package mail". The tiles in the different templates may be identical, and may include conditions, operations and results, rule previews, and operation button fields, for example.
Taking the expressive language template as an example, the configuration interface may be as shown in fig. 3-2. The method can comprise a plurality of configuration options such as terminal selection, preconditions, operation mode setting, component association relation information setting, rule preview and the like.
With respect to the configuration of the preconditions, as shown in fig. 3-3, the preset basic feature dimensions of the system may be provided for customization. For example, in a network sales system product, the basic features may include a buyer, a commodity, a seller, an order, and the like. The selected basic features default to no expression, but the system can provide the existing business features under the current component for reference and quick customization. The business features (e.g., buyer feature 1, buyer feature 2, commodity feature 1, commodity feature 2, etc. shown in fig. 3-3) generated on the basis of the basic features may be stored in the full-link platform, and the basic features and the business features preset by the system are provided with interface support by the full-link platform, while the full-link platform may also provide new business features with interface support. The feature expression can be assembled by the research and development platform provided in the embodiment of the application and transmitted to the full-link platform for analysis, and the assembling result can comprise: expected feature values, operators, expression order, whether the data is locked, etc. In short, the configuration of the relevant information of the characteristic value of the business rule can be realized through the configuration of the 'precondition'.
With respect to operation configuration, a specific configuration interface may be shown in fig. 3-4, where specific operation and result implementation may be provided by a test platform (e.g., matrix platform, etc.), and the development platform in the embodiment of the present application only needs to complete operation, analysis and identification of a result, and customization of a result check point. In specific implementation, the basic operation of the page to which the component belongs and the basic operation of the component can be automatically brought, a default selection value (provided by a system) exists, and the order is confirmed by default selection of the following single page. One operation may support multiple result verifications, one rule may support multiple operations, and the server in the embodiments of the present application may maintain the order of the operations and pass the order to the test platform. The check points can provide inquiry in component dimension, and the existing check points of the system can be input in an enumeration form for the check points selected and quantized by the user.
It should be noted that the usage scenarios of the operation modes can be mainly divided into the following three scenarios:
1. no operational mode settings are required, for example: under a single commodity and a single scene, the integral component selects integral operation, and the system defaults to full use without selection of a user;
2. the operation mode needs to be set, for example: under the single commodity bill scene, the invoice component selects the operation of 'invoicing', and a user needs to select invoice heads, invoice types and invoice contents of the invoice component;
3. The operation mode needs to be set, for example: under the single scene under multiple commodities, the "in-flower stage" component selects the "modify in-flower stage" operation, and the user needs to select which commodity to modify.
After the configuration of the characteristic values and the operation mode information is completed, the two block contents can be automatically packaged to generate business rules, and previews of the rules can be provided.
After the above configuration is completed, the contents of the configuration may be saved by clicking the "save" button in fig. 3-2. In addition, in the expression page, an option of generating test cases can be provided, and a user can generate specific test cases by clicking the option.
S203: and generating a product demand document according to the configuration information.
After the above configuration of the component set and rule set and PRD document template is completed, a specific PRD document may be automatically generated. Therefore, according to the embodiment of the application, the PRD document can be generated in a configuration mode, so that standardization and standardization of the PDR document are facilitated.
In addition, in the development platform provided in the embodiment of the present application, a search function may also be provided to support queries such as component types (base component, service component), component names, supported terminals (PC, native, H, etc.), platforms (shopping guide, forward transaction, reverse transaction), pages (order, shopping cart, refund application, etc.), component states (newly added, in use, archived, deleted), and the like. In addition, various operations can be provided, including a global new component, a batch selection component, a batch deletion component, a batch archiving component and the like; there are deletion components, archiving components, business rule details, etc. for a single component.
In the actual product development process, after a developer finishes the development of a product demand document, a tester needs to write a test case according to the product demand document, wherein the test case is a set of test input, execution conditions and expected results formulated for a certain test target. The test cases are the test cores of the products, and the quantity and the quality of the test cases directly determine the development quality of the products, so that the development of the test cases is also an important link of the development of the products. The traditional mode is that test cases are manually written by testers according to personal development experience, the quantity and quality of the developed test cases cannot meet product requirements due to the fact that personal experience is irregular, and furthermore, the efficiency of manually writing the test cases cannot meet the development requirements.
In the embodiment of the application, since the PRD document is automatically generated in a configuration manner, configuration information in the lower document, including information such as a component set and a rule set, can be saved when the PRD document is saved. Therefore, the test case can be automatically generated on the basis of the configuration information. Specifically, the server may obtain the topology relation information between the services in advance, and may further set a related algorithm in advance, so that a test case for performing a product test may be generated according to the configuration information associated with the product requirement document.
Specifically, the server side can determine service information related to service rules of the product according to a preset product service topological relation diagram; furthermore, according to the service information, the configuration information in the product demand document and the service relationship topological relation information, a test case corresponding to the service rule can be generated.
In particular implementations, a variety of operational options may be provided for initiating test case/test script generation. For example, in one mode, a case can be generated by pressing a product key, specifically, a first operation option for generating a test case for a specified product can be provided, and when a corresponding request is received through the first operation option, the corresponding test case is generated according to each business rule associated with the specified product. For example, specifically, a "use case management" link may be located behind each PRD of the "product management" page, and use case generation may be triggered after clicking [ use case management ]. Specifically, a case set can be generated according to each service rule, and the case management list is skipped after the case set is successfully generated. The use case catalogs can be generated according to the tree structures of the products, the pages, the component sets and the rule sets, and each rule corresponds to a leaf catalogue at the bottommost layer. For the structured rule containing the characteristic value, the corresponding test script can be generated while the test case is generated, and the test case and the test script can be in one-to-one association correspondence. Of course, for unstructured rules without feature values, only test cases without corresponding scripts can be generated. And then, related test personnel and other users can correlate the test data for the test cases in a mode of manually correlating the test data, so that corresponding test scripts are obtained, and then, the product test is carried out by executing the test scripts.
In another implementation manner, a second operation option for generating the test case can be provided for each service rule under each component associated with the specified product, so that when a request for generating the test case for the specified service rule is received through the second operation option, the test case is generated for the specified service rule. In particular implementations, each rule for each component within the product may have a corresponding [ generate use case ] operation option. In concrete implementation, the use case catalogue can be generated according to the tree structures of the product, the page, the component set and the rule set, and the generated use cases are stored in the catalogue of the corresponding rule.
Whether the test case is generated for one key of the whole product or the specific business rule, each rule can generate a plurality of test cases.
To facilitate understanding of test cases, an example of a "system login" business rule is illustrated below, and one test case is generated as follows:
case name: logging in a system;
the pre-condition is as follows: the user name exists and the password is correct;
test data: existing users and passwords: test/hello1234;
test step 1: opening an IE browser, inputting a corresponding target address in an address bar, and entering a system login page;
Test step 2: inputting a user name test and inputting a password hello1234;
and (3) testing: clicking "login";
the expected results are: the login is successful.
In an alternative implementation, the server may generate different numbers of test cases according to different business rules. For example, when a certain business rule does not relate to a product business, the server side may generate a test case, such as a system login test case, for the business rule; when a certain business rule relates to a specific product business, the server side can generate a plurality of test cases aiming at the business rule so as to comprehensively cover the product business and ensure the effectiveness and stability of the product.
When a certain business rule relates to a specific product business, the server side can generate a test case for each business rule of the product according to a pre-established product business topological relation diagram and configuration information of the business rule included in the product; the product service topological relation diagram can be a relation diagram generated according to the association relation between the services of the actual product; the product service topological relation diagram reflects the real service association condition, and the service side can automatically expand a plurality of test cases for one service rule by using the product service topological relation diagram.
Specifically, in the embodiment of the present application, since each service rule is structured to be represented as three major parts, that is, a precondition, an operation step, and an expected result, the server encapsulates, at the bottom layer, codes of corresponding feature values and verification methods for the three parts, where the precondition corresponds to the feature values, and the operation step and the expected result correspond to the codes of the verification methods, respectively, so that a relationship between product services related to one service rule can be expanded to multiple test cases.
By way of example, taking the service rule of "the electric appliance city commodity order must be invoiced" as an example, because the electric appliance city commodity service is associated with specific services such as large household appliances, small household appliances, 3C numbers, etc., when generating test cases, 3 test cases can be generated: 1. the commodity order of the large household appliance must be invoiced; 2. the commodity order of the small household appliance must be invoiced; 3. the 3C digital commodity order must be invoiced, etc.
It should be noted that one business rule may correspond to a plurality of test cases, but one test case may correspond to only one business rule. For example, taking an item detail page as an example, the components associated with the item detail page may have a shipping cost component, an item master diagram component, an item price component, and so on, where the shipping cost component may include a plurality of business rules: 1. the detailed page freight of the commodity in the supermarket shows that the commodity is "full 88 package mail"; 2. common heaven cat commodity, freight show corresponding price, such as freight package mail to Hangzhou, freight 5 yuan to Guangzhou, etc.; the server side can generate a plurality of test cases for the business rule 1 according to the product business topological relation diagram; meanwhile, a plurality of test cases can be generated aiming at the business rule 2.
It should be noted that, when the test case is generated for the business rule which is not changed, the test case does not need to be generated again, and the previous test case can be directly imported into the test case list of the existing product. Meanwhile, the server side can support the user to view the generated test cases.
Through the method, the server side can automatically generate a plurality of test cases through the product service topological relation diagram and the structured service rules, and the test cases are comprehensive and specific enough and can achieve a good test effect. The traditional test case generation needs a tester to write manually according to experience, the efficiency is low, and the test effect is not ideal due to the influence of human factors. Therefore, in the embodiment of the application, when the PRD document is automatically generated in a configuration mode, the configuration information and the pre-stored service topology relation information can be utilized to automatically generate the test case, so that the overall research and development efficiency can be improved, and the product quality can be ensured.
It should be noted that, in practical application, besides the test case, a test script is needed in the process of testing a product, where the test script generally refers to a series of instructions for a specific test, and these instructions may be executed by a testing tool to test whether the quality of the product meets the requirement. The traditional mode is that test scripts are manually written by testers according to personal development experience, false test data are required to be written when the test scripts are written, the developed test scripts are unsuitable due to the fact that personal experience is uneven, or the test data are unsuitable, so that the test cannot be normally operated, and moreover, the efficiency of manually writing the test scripts cannot meet development requirements.
In the embodiment of the application, because the structural expression of the business rule is supported, the structural expression comprises a precondition, an operation step and an expected result, and corresponding codes are packaged at the bottom layer, the service side generates one or more test cases for one business rule through a business-business association topological graph; further, for the structured test case, real service data can be screened out as test data by utilizing the characteristic value corresponding to the precondition of the structured test case, and then, a test script is automatically generated according to the test data and the packaged codes.
Of course, for the unstructured service rule, namely the service rule of natural language, the service rule cannot filter test data through the characteristic value because of no structuring, and the generation of the test script needs corresponding test data, so that the unstructured service rule can automatically generate the test case but cannot generate the corresponding test script.
Therefore, in the embodiment of the application, for the service rule which is structured and expressed, the server can automatically call the real data running on line as the test data to automatically generate the test script, so that the script generation efficiency is improved, and meanwhile, the test effectiveness can be ensured. After the test script is executed, a corresponding test report can be generated, and the number of successful test cases and the number of failed test cases can be read in the test report. Meanwhile, a user can search the specific reasons of failure in the failure test case log, so that the user can quickly locate errors and timely modify the errors, and the quality of products is guaranteed.
By using the method, the server can automatically generate the test cases and simultaneously generate the corresponding test scripts, and can call the online running data as the test data, so that the authenticity and the effectiveness of the test are ensured, the user can rapidly develop the test work, and the test efficiency is improved.
According to the method for generating the product demand document, the unified standard structured product demand document development mode is provided for the product developer, the developer is guided to quickly know the service through the structured configuration interface, the product demand document is quickly generated, and the corresponding test case and test script are automatically generated according to the service rule and the service relation topological graph in the product demand document.
Example two
As described above, after the configuration of the product requirements is completed in the manner provided in the embodiments of the present application, the test case may also be directly generated according to such configuration information, without waiting until a specific PRD document is generated, and then regenerating the test case. Therefore, the second embodiment mainly provides a method for generating product test information, referring to fig. 4, the method specifically may include:
S401: providing an operational option for configuring product requirements;
s402: receiving configuration information of product requirements through the operation options, wherein the configuration information comprises a component set required by the product and a service rule set under each component;
s403: and generating a test case for carrying out product test according to the configuration information and the pre-obtained topological relation information between the services.
In specific implementation, if the service rule is a structured rule including a feature value, test data can be screened out from real service data according to the feature value, and a test script is generated for a test case corresponding to the service rule according to the test data.
For the specific implementation of each step in the second embodiment, reference may be made to the description in the first embodiment, and the description is omitted here.
Corresponding to the method, the embodiment of the application also provides a device for generating the product demand document, referring to fig. 5, the device specifically may include:
an operation option providing unit 501 for providing operation options for configuring product requirements;
a configuration information receiving unit 502, configured to receive product requirement configuration information through the operation options, where the configuration information includes a product requirement document template, a component set, and a service rule set under each component required by a product;
A requirement document generating unit 503, configured to generate a product requirement document according to the configuration information.
In particular, the apparatus may further include:
and the test case generating unit is used for generating a test case for carrying out product testing according to the configuration information associated with the product demand document and the pre-acquired topological relation information among the services.
Specifically, the test case generating unit may specifically include:
a first operation option providing subunit for providing a first operation option for generating test cases for specified products;
and the first generation subunit is used for respectively generating corresponding test cases according to each business rule associated with the specified product when receiving the corresponding request through the first operation option.
Alternatively, the test case generating unit may specifically include:
a second operation option providing subunit, configured to provide, for each business rule under each component associated with the specified product, a second operation option for generating a test case respectively;
and the second generating subunit is used for generating the test case for the specified business rule when receiving the request for generating the test case for the specified business rule through the second operation option.
In addition, the apparatus may further include:
a rule judging unit, configured to determine whether the service rule is a structured rule including a feature value;
and the first test script generating unit is used for screening test data from the real service data according to the characteristic value and generating a test script for the test case corresponding to the service rule according to the test data if the test script is generated.
Alternatively, it may further include:
and the second test script generating unit is used for receiving the test data submitted for the test case corresponding to the unstructured business rule and generating a corresponding test script for the test case according to the test data.
Furthermore, the method may further comprise:
and the test script execution unit is used for obtaining a test result by executing the test script in a preset test platform.
In a specific implementation, the operation option providing unit may specifically be configured to:
providing an operational option for selecting from existing products;
the configuration information receiving unit may specifically be configured to:
receiving selected target existing product information through the operation options;
providing the configuration information related to the target existing product and operation options for editing on the basis of the configuration information related to the target existing product so as to determine the configuration information of the current product by editing on the basis of the configuration information related to the target existing product.
Alternatively, the operation option providing unit may specifically be configured to:
providing operation options for brand new customization of the product, and optionally a product demand document template and page information;
the configuration information receiving unit may specifically be configured to:
receiving a selected target product demand document template and a related target page through the operation options;
providing a basic component information set associated with the target page, and operating options for editing the basic component so as to determine a component set and a service rule set of a current product by editing the basic component information associated with the target page.
From another point of view, the operation option providing unit may specifically be configured to:
providing operation options for editing the component set so as to generate a component tree according to the editing result of the component set; wherein, the operation options for editing the component set include: the operation options selected from the known components, the operation options for adding new components, and the operation options for customizing the original components.
In addition, the operation option providing unit may be further configured to:
After receiving the operation executed on the target component in the component tree, an interface for editing the business rule of the target component is provided so as to determine the business rule set corresponding to the target component.
The interface for editing the business rule of the target component comprises the following steps: and the operation options are used for configuring the component preconditions, the component operation modes and/or the component association relation information so as to generate structured business rule information according to the component preconditions and the operation mode information, wherein the preconditions are used for configuring the characteristic value information of the business rule.
In addition, the apparatus may further include:
a search unit for providing operational options for conducting a search, the dimensions of the search comprising: component category, component name, supported terminal, platform, page, component status.
Corresponding to the embodiment, the embodiment of the application also provides a device for generating product test information, referring to fig. 6, the device may include:
an operation option providing unit 601 for providing operation options for configuring product requirements;
a configuration information receiving unit 602, configured to receive, through the operation option, configuration information of a product requirement, where the configuration information includes a set of components required by the product and a set of business rules under each component;
The test case generating unit 603 is configured to generate a test case for performing a product test according to the configuration information and the pre-obtained topology relationship information between services.
In particular, the apparatus may further include:
a rule judging unit, configured to determine whether the service rule is a structured rule including a feature value;
and the test script generating unit is used for screening test data from the real service data according to the characteristic value and generating a test script for the test case corresponding to the service rule according to the test data if the test script is generated.
In addition, corresponding to the first embodiment, the embodiment of the application further provides a computer system, which includes:
one or more processors; and
a memory associated with the one or more processors, the memory for storing program instructions that, when read for execution by the one or more processors, perform the operations of:
providing an operational option for configuring product requirements;
receiving product demand configuration information through the operation options, wherein the configuration information comprises a product demand document template, a component set and a service rule set under each component required by a product;
And generating a product demand document according to the configuration information.
Corresponding to the embodiment, the embodiment of the application also provides a computer system, which comprises:
one or more processors; and
a memory associated with the one or more processors, the memory for storing program instructions that, when read for execution by the one or more processors, perform the operations of:
providing an operational option for configuring product requirements;
receiving product demand configuration information through the operation options, wherein the configuration information comprises a product demand document template, a component set and a service rule set under each component required by a product;
and generating a test case for carrying out product test according to the configuration information and the pre-obtained topological relation information between the services.
Fig. 7 illustrates an architecture of a computer system, which may include a processor 710, a video display adapter 711, a disk drive 712, an input/output interface 713, a network interface 714, and a memory 720, among others. The processor 710, the video display adapter 711, the disk drive 712, the input/output interface 713, the network interface 714, and the memory 720 may be communicatively connected via a communication bus 730.
The processor 710 may be implemented by a general-purpose CPU (Central Processing Unit ), a microprocessor, an application-specific integrated circuit (Application Specific Integrated Circuit, ASIC), or one or more integrated circuits, etc., for executing related programs to implement the technical solutions provided in the present application.
The Memory 720 may be implemented in the form of ROM (Read Only Memory), RAM (Random Access Memory ), static storage device, dynamic storage device, or the like. Memory 720 may store an operating system 721 for controlling the operation of computer system 700, and a Basic Input Output System (BIOS) for controlling the low-level operation of computer system 700. In addition, a web browser 723, a data storage management system 724, a product demand document processing system 725, and the like may also be stored. The product requirement document processing system 725 may be an application program that specifically implements the operations of the foregoing steps in the embodiments of the present application. In general, when implemented in software or firmware, the relevant program code is stored in memory 720 and executed by processor 710.
The input/output interface 713 is used to connect with an input/output module to enable information input and output. The input/output module may be configured as a component in a device (not shown) or may be external to the device to provide corresponding functionality. Wherein the input devices may include a keyboard, mouse, touch screen, microphone, various types of sensors, etc., and the output devices may include a display, speaker, vibrator, indicator lights, etc.
The network interface 714 is used to connect communication modules (not shown) to enable communication interactions of the device with other devices. The communication module may implement communication through a wired manner (such as USB, network cable, etc.), or may implement communication through a wireless manner (such as mobile network, WIFI, bluetooth, etc.).
Bus 730 includes a path to transfer information between various components of the device (e.g., processor 710, video display adapter 711, disk drive 712, input/output interface 713, network interface 714, and memory 720).
In addition, the computer system 700 may also obtain information of specific retrieval conditions from the virtual resource object retrieval condition information database 741 for making condition judgment, and so on.
It should be noted that although the above devices illustrate only the processor 710, the video display adapter 711, the disk drive 712, the input/output interface 713, the network interface 714, the memory 720, the bus 730, etc., the device may include other components necessary to achieve proper operation in an implementation. Furthermore, it will be understood by those skilled in the art that the above-described apparatus may include only the components necessary to implement the present application, and not all the components shown in the drawings.
It is noted that relational terms such as first and second, and the like are used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Moreover, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element. The application may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. The application may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.
In this specification, each embodiment is described in a progressive manner, and identical and similar parts of each embodiment are all referred to each other, and each embodiment mainly describes differences from other embodiments. In the practical application process, part or all of the units can be selected according to practical needs to realize the purpose of the scheme of the embodiment, and one of ordinary skill in the art can understand and implement the scheme without carrying out creative labor.
The foregoing is merely exemplary of the application and it should be noted that modifications and adaptations to those skilled in the art may be made without departing from the principles of the application and are intended to be comprehended within the scope of the application.

Claims (19)

1. A method for generating a product demand document, comprising:
providing an operational option for configuring product requirements; the configuration interface corresponding to the operation option comprises: different configuration interfaces are constructed according to the hierarchical relationship among the products, the pages, the components and the business rules; one product relates to one or more pages, a plurality of components are associated in one page, and a plurality of business rules are included in one component;
Receiving product demand configuration information through the operation options, wherein the configuration information comprises a product demand document template, a component set and a service rule set under each component required by a product;
generating a product demand document according to the configuration information;
wherein a component is a collection of interrelated business rules; the assembly comprises: component display example graphs, component introductions, and business rules; the business rule comprises: characteristic values, operating steps, and expected results; the configuration interface comprises: a first layer configuration interface generated according to the product configuration control, a second layer configuration interface generated according to the page configuration control, and a third layer configuration interface generated according to the component configuration control; the first layer configuration interface is used for bearing configuration controls for configuring basic information of products; the second layer configuration interface is used for bearing configuration controls for configuring page related information; the third layer configuration interface is used for bearing configuration control of configuration component related information.
2. The method as recited in claim 1, further comprising:
and generating a test case for carrying out product testing according to the configuration information associated with the product demand document and the pre-obtained topological relation information among the services.
3. The method of claim 2, wherein the step of determining the position of the substrate comprises,
the generating test cases for performing product testing includes:
providing a first operation option for generating test cases for a specified product;
when receiving a corresponding request through the first operation option, respectively generating corresponding test cases according to each business rule associated with the specified product.
4. The method of claim 2, wherein the step of determining the position of the substrate comprises,
the generating test cases for performing product testing includes:
providing a second operation option for generating a test case for each business rule under each component associated with the appointed product;
and when receiving a request for generating test cases for the specified business rules through the second operation options, generating the test cases for the specified business rules.
5. The method as recited in claim 2, further comprising:
determining whether the business rule is a structured rule containing a characteristic value;
if yes, screening test data from the real service data according to the characteristic value, and generating a test script for the test case corresponding to the service rule according to the test data.
6. The method of claim 2, wherein the step of determining the position of the substrate comprises,
and receiving test data submitted for the test case corresponding to the unstructured business rule, and generating a corresponding test script for the test case according to the test data.
7. The method according to claim 5 or 6, further comprising:
and executing the test script in a preset test platform to obtain a test result.
8. The method according to any one of claim 1 to 6, wherein,
the providing operation options for configuring product requirements includes:
providing an operational option for selecting from existing products;
the receiving product demand configuration information through the operation options comprises the following steps:
receiving selected target existing product information through the operation options;
providing the configuration information related to the target existing product and operation options for editing on the basis of the configuration information related to the target existing product so as to determine the configuration information of the current product by editing on the basis of the configuration information related to the target existing product.
9. The method according to any one of claim 1 to 6, wherein,
The providing operation options for configuring product requirements includes:
providing operation options for brand new customization of the product, and optionally a product demand document template and page information;
the receiving product demand configuration information through the operation options comprises the following steps:
receiving a selected target product demand document template and a related target page through the operation options;
providing a basic component information set associated with the target page, and operating options for editing the basic component so as to determine a component set and a service rule set of a current product by editing the basic component information associated with the target page.
10. The method according to any one of claim 1 to 6, wherein,
the providing operation options for configuring product requirements includes:
providing operation options for editing the component set so as to generate a component tree according to the editing result of the component set; wherein, the operation options for editing the component set include: the operation options selected from the known components, the operation options for adding new components, and the operation options for customizing the original components.
11. The method of claim 10, wherein the step of determining the position of the first electrode is performed,
the providing operation options for configuring product requirements further comprises:
after receiving the operation executed on the target component in the component tree, an interface for editing the business rule of the target component is provided so as to determine the business rule set corresponding to the target component.
12. The method of claim 11, wherein the step of determining the position of the probe is performed,
the interface for editing the business rule of the target component comprises the following steps: and the operation options are used for configuring the component preconditions, the component operation modes and/or the component association relation information so as to generate structured business rule information according to the component preconditions and the operation mode information, wherein the preconditions are used for configuring the characteristic value information of the business rule.
13. The method according to any one of claims 1 to 6, further comprising:
providing operational options for conducting a search, the dimensions of the search including: component category, component name, supported terminal, platform, page, component status.
14. A method of generating product test information, comprising:
Providing an operational option for configuring product requirements; the configuration interface corresponding to the operation option comprises: different configuration interfaces are constructed according to the hierarchical relationship among the products, the pages, the components and the business rules; one product relates to one or more pages, a plurality of components are associated in one page, and a plurality of business rules are included in one component;
receiving configuration information of product requirements through the operation options, wherein the configuration information comprises a component set required by the product and a service rule set under each component;
generating a test case for carrying out product test according to the configuration information and the pre-obtained topological relation information between the services;
wherein a component is a collection of interrelated business rules; the assembly comprises: component display example graphs, component introductions, and business rules; the business rule comprises: characteristic values, operating steps, and expected results; the configuration interface comprises: a first layer configuration interface generated according to the product configuration control, a second layer configuration interface generated according to the page configuration control, and a third layer configuration interface generated according to the component configuration control; the first layer configuration interface is used for bearing configuration controls for configuring basic information of products; the second layer configuration interface is used for bearing configuration controls for configuring page related information; the third layer configuration interface is used for bearing configuration control of configuration component related information.
15. The method as recited in claim 14, further comprising:
determining whether the business rule is a structured rule containing a characteristic value;
if yes, screening test data from the real service data according to the characteristic value, and generating a test script for the test case corresponding to the service rule according to the test data.
16. A product demand document generation apparatus, comprising:
an operation option providing unit for providing operation options for configuring product requirements; the configuration interface corresponding to the operation option comprises: different configuration interfaces are constructed according to the hierarchical relationship among the products, the pages, the components and the business rules; one product relates to one or more pages, a plurality of components are associated in one page, and a plurality of business rules are included in one component;
the configuration information receiving unit is used for receiving product demand configuration information through the operation options, wherein the configuration information comprises a product demand document template, a component set and a service rule set under each component required by a product;
a demand document generation unit for generating a product demand document according to the configuration information;
Wherein a component is a collection of interrelated business rules; the assembly comprises: component display example graphs, component introductions, and business rules; the business rule comprises: characteristic values, operating steps, and expected results; the configuration interface comprises: a first layer configuration interface generated according to the product configuration control, a second layer configuration interface generated according to the page configuration control, and a third layer configuration interface generated according to the component configuration control; the first layer configuration interface is used for bearing configuration controls for configuring basic information of products; the second layer configuration interface is used for bearing configuration controls for configuring page related information; the third layer configuration interface is used for bearing configuration control of configuration component related information.
17. A product test information generating apparatus, comprising:
an operation option providing unit for providing operation options for configuring product requirements; the configuration interface corresponding to the operation option comprises: different configuration interfaces are constructed according to the hierarchical relationship among the products, the pages, the components and the business rules; one product relates to one or more pages, a plurality of components are associated in one page, and a plurality of business rules are included in one component;
The configuration information receiving unit is used for receiving the configuration information of the product requirement through the operation options, wherein the configuration information comprises a component set required by the product and a service rule set under each component;
the test case generating unit is used for generating a test case for carrying out product test according to the configuration information and the pre-obtained topological relation information among the services;
wherein a component is a collection of interrelated business rules; the assembly comprises: component display example graphs, component introductions, and business rules; the business rule comprises: characteristic values, operating steps, and expected results; the configuration interface comprises: a first layer configuration interface generated according to the product configuration control, a second layer configuration interface generated according to the page configuration control, and a third layer configuration interface generated according to the component configuration control; the first layer configuration interface is used for bearing configuration controls for configuring basic information of products; the second layer configuration interface is used for bearing configuration controls for configuring page related information; the third layer configuration interface is used for bearing configuration control of configuration component related information.
18. A computer system, comprising:
One or more processors; and
a memory associated with the one or more processors, the memory for storing program instructions that, when read for execution by the one or more processors, perform the operations of:
providing an operational option for configuring product requirements; the configuration interface corresponding to the operation option comprises: different configuration interfaces are constructed according to the hierarchical relationship among the products, the pages, the components and the business rules; one product relates to one or more pages, a plurality of components are associated in one page, and a plurality of business rules are included in one component;
receiving product demand configuration information through the operation options, wherein the configuration information comprises a product demand document template, a component set and a service rule set under each component required by a product;
generating a product demand document according to the configuration information;
wherein a component is a collection of interrelated business rules; the assembly comprises: component display example graphs, component introductions, and business rules; the business rule comprises: characteristic values, operating steps, and expected results; the configuration interface comprises: a first layer configuration interface generated according to the product configuration control, a second layer configuration interface generated according to the page configuration control, and a third layer configuration interface generated according to the component configuration control; the first layer configuration interface is used for bearing configuration controls for configuring basic information of products; the second layer configuration interface is used for bearing configuration controls for configuring page related information; the third layer configuration interface is used for bearing configuration control of configuration component related information.
19. A computer system, comprising:
one or more processors; and
a memory associated with the one or more processors, the memory for storing program instructions that, when read for execution by the one or more processors, perform the operations of:
providing an operational option for configuring product requirements; the configuration interface corresponding to the operation option comprises: different configuration interfaces are constructed according to the hierarchical relationship among the products, the pages, the components and the business rules; one product relates to one or more pages, a plurality of components are associated in one page, and a plurality of business rules are included in one component;
receiving product demand configuration information through the operation options, wherein the configuration information comprises a product demand document template, a component set and a service rule set under each component required by a product;
generating a test case for carrying out product test according to the configuration information and the pre-obtained topological relation information between the services;
wherein a component is a collection of interrelated business rules; the assembly comprises: component display example graphs, component introductions, and business rules; the business rule comprises: characteristic values, operating steps, and expected results; the configuration interface comprises: a first layer configuration interface generated according to the product configuration control, a second layer configuration interface generated according to the page configuration control, and a third layer configuration interface generated according to the component configuration control; the first layer configuration interface is used for bearing configuration controls for configuring basic information of products; the second layer configuration interface is used for bearing configuration controls for configuring page related information; the third layer configuration interface is used for bearing configuration control of configuration component related information.
CN201810217550.7A 2018-03-09 2018-03-09 Method and device for generating product demand document and test information Active CN110244934B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201810217550.7A CN110244934B (en) 2018-03-09 2018-03-09 Method and device for generating product demand document and test information

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201810217550.7A CN110244934B (en) 2018-03-09 2018-03-09 Method and device for generating product demand document and test information

Publications (2)

Publication Number Publication Date
CN110244934A CN110244934A (en) 2019-09-17
CN110244934B true CN110244934B (en) 2024-01-19

Family

ID=67882375

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201810217550.7A Active CN110244934B (en) 2018-03-09 2018-03-09 Method and device for generating product demand document and test information

Country Status (1)

Country Link
CN (1) CN110244934B (en)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112818628B (en) * 2020-12-30 2024-08-06 黄国勳 Automatic developing method and system for design rule of integrated circuit manufacturing process
CN113051868A (en) * 2021-04-02 2021-06-29 黄国勳 DRC automatic interface realization method for integrated circuit manufacturing process rule verification

Citations (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101361088A (en) * 2005-11-23 2009-02-04 瑞士银行股份有限公司 Computer implemented system for creating, processing and managing structured data sets
CN101377737A (en) * 2007-08-28 2009-03-04 上海宝信软件股份有限公司 Resource management apparatus of application system
CN103412853A (en) * 2013-08-05 2013-11-27 北京信息科技大学 Method for automatically generating test cases aiming at document converters
CN103488482A (en) * 2013-09-16 2014-01-01 深圳市龙视传媒有限公司 Method and device for generating test cases
JP2014171053A (en) * 2013-03-01 2014-09-18 Sky Com:Kk Electronic document container data file, electronic document container data file generating apparatus, electronic document container data file generating program, server apparatus, and electronic document container data file generating method
CN104572449A (en) * 2014-12-23 2015-04-29 中国移动通信集团广东有限公司 Automatic test method based on case library
CN104699608A (en) * 2015-03-10 2015-06-10 于秀山 Automatic test method and device for graphic user interface software
CN106250164A (en) * 2016-08-16 2016-12-21 广州仕邦人力资源有限公司 A kind of code generating method based on requirement documents and device
CN106294150A (en) * 2016-08-09 2017-01-04 北京神州绿盟信息安全科技股份有限公司 A kind of test loading method and device
CN106570189A (en) * 2016-11-14 2017-04-19 广东电网有限责任公司 Convenient management method for computer application systems and documents
CN107729047A (en) * 2017-10-11 2018-02-23 锐捷网络股份有限公司 Document structure tree method and device

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7913230B2 (en) * 2007-01-31 2011-03-22 Oracle International Corporation Computer-implemented methods and systems for generating software testing documentation and test results management system using same
US9690770B2 (en) * 2011-05-31 2017-06-27 Oracle International Corporation Analysis of documents using rules

Patent Citations (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101361088A (en) * 2005-11-23 2009-02-04 瑞士银行股份有限公司 Computer implemented system for creating, processing and managing structured data sets
CN101377737A (en) * 2007-08-28 2009-03-04 上海宝信软件股份有限公司 Resource management apparatus of application system
JP2014171053A (en) * 2013-03-01 2014-09-18 Sky Com:Kk Electronic document container data file, electronic document container data file generating apparatus, electronic document container data file generating program, server apparatus, and electronic document container data file generating method
CN103412853A (en) * 2013-08-05 2013-11-27 北京信息科技大学 Method for automatically generating test cases aiming at document converters
CN103488482A (en) * 2013-09-16 2014-01-01 深圳市龙视传媒有限公司 Method and device for generating test cases
CN104572449A (en) * 2014-12-23 2015-04-29 中国移动通信集团广东有限公司 Automatic test method based on case library
CN104699608A (en) * 2015-03-10 2015-06-10 于秀山 Automatic test method and device for graphic user interface software
CN106294150A (en) * 2016-08-09 2017-01-04 北京神州绿盟信息安全科技股份有限公司 A kind of test loading method and device
CN106250164A (en) * 2016-08-16 2016-12-21 广州仕邦人力资源有限公司 A kind of code generating method based on requirement documents and device
CN106570189A (en) * 2016-11-14 2017-04-19 广东电网有限责任公司 Convenient management method for computer application systems and documents
CN107729047A (en) * 2017-10-11 2018-02-23 锐捷网络股份有限公司 Document structure tree method and device

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
Requirements for the data transfer during the examination of design documentation;Irina Karakozova et.al;《MATEC Web Conf.》;第106卷;第1-9页 *
产品开发过程与数据集成管理模型的研究;刘正琼等;《工程图学学报》;20091215(第06期);第187-191页 *
浅谈基于B/S的电力系统业务传递审批软件设计;侯剑;;电子世界(18);第147-149页 *

Also Published As

Publication number Publication date
CN110244934A (en) 2019-09-17

Similar Documents

Publication Publication Date Title
CN108153670B (en) Interface testing method and device and electronic equipment
CN107370786B (en) General information management system based on micro-service architecture
US11922382B2 (en) Transaction system having a serverless architecture that provides multi-language multi-platform transaction support for multiple vendors in conjunction with a cloud-based computing platform
US11276097B1 (en) Canonical order management system
US8799854B2 (en) Reusing software development assets
US9043232B1 (en) Associating item images with item catalog data
US11036682B2 (en) Flexible energy information aggregation
KR102225729B1 (en) Product information processing apparatus for multiple online shopping mall product registration and method thereof
CN106326243B (en) Data processing method and device
TW201405452A (en) Workflow management device and workflow management method
US10713070B2 (en) Systems and methods for capturing and visualizing user interactions across devices
CN111427577A (en) Code processing method and device and server
US20210241357A1 (en) Customizable and extensible managed integration platform
WO2010127552A1 (en) Service-oriented application system and communicating method, creator and creating method thereof
US20210124752A1 (en) System for Data Collection, Aggregation, Storage, Verification and Analytics with User Interface
CN111190905A (en) Database table processing method and device and electronic equipment
CN111861598A (en) Object display method and device, electronic equipment and readable medium
CN111984882A (en) Data processing method, system and equipment
CN110244934B (en) Method and device for generating product demand document and test information
CN113535101B (en) Print file generation method and device, storage medium and electronic equipment
CN113434063A (en) Information display method, device and equipment
CN115202711B (en) Data release method and system
US8260782B2 (en) Data element categorization in a service-oriented architecture
CN113296912A (en) Task processing method, device and system, storage medium and electronic equipment
KR20220166084A (en) Meter data unification management system

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant