CN105487979A - Test tool management method and user terminal - Google Patents
Test tool management method and user terminal Download PDFInfo
- Publication number
- CN105487979A CN105487979A CN201510874109.2A CN201510874109A CN105487979A CN 105487979 A CN105487979 A CN 105487979A CN 201510874109 A CN201510874109 A CN 201510874109A CN 105487979 A CN105487979 A CN 105487979A
- Authority
- CN
- China
- Prior art keywords
- tool
- tool identification
- test
- triggered
- file
- 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.)
- Pending
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Test And Diagnosis Of Digital Computers (AREA)
Abstract
The embodiment of the invention discloses a test tool management method and a user terminal, wherein the method comprises the following steps: obtaining a triggered tool identifier from a pre-set test tool catalogue, and obtaining a tool path corresponding to the triggered tool identifier; obtaining a test file corresponding to the triggered tool identifier based on the tool path corresponding to the triggered tool identifier; loading the test file corresponding to the triggered tool identifier by using a preset assembly mode; and generating a test interface corresponding to the triggered tool identifier after successfully loading. By adopting the invention, the searching efficiency of the test file can be increased; and thus, the test efficiency of a terminal application product is improved.
Description
Technical field
The present invention relates to field of computer technology, particularly relate to a kind of testing tool management method and user terminal.
Background technology
Along with computer technology is constantly developed and perfect, terminal applies product miscellaneous is developed to meet the different demands in people's life, along with the complexity of product form increases, tester needs to use multiple testing tool to carry out the tracking and testing of terminal applies product simultaneously, but for the management of the corresponding test file of testing tool, often need the custom relying on tester, easy appearance is due to test file dispersion storage, cause to find corresponding tool path fast to obtain test file, reduce the search efficiency of test file, and then the testing efficiency reduced terminal applies product.
Summary of the invention
The embodiment of the present invention provides a kind of testing tool management method and user terminal, can improve the search efficiency of test file, and then promotes the testing efficiency to terminal applies product.
Embodiment of the present invention first aspect provides a kind of testing tool management method, can comprise:
In default testing tool catalogue, obtain triggered tool identification, and obtain tool path corresponding to described triggered tool identification;
Test file corresponding to described triggered tool identification is obtained based on the tool path that described triggered tool identification is corresponding;
Adopt and preset test file corresponding to described the triggered tool identification of assembly mode loading;
Generate test interface corresponding to described triggered tool identification loading successfully.
Embodiment of the present invention second aspect provides a kind of user terminal, can comprise:
Path acquiring unit, for obtaining triggered tool identification in default testing tool catalogue, and obtains tool path corresponding to described triggered tool identification;
First file obtaining unit, obtains test file corresponding to described triggered tool identification for the tool path corresponding based on described triggered tool identification;
Files loading unit, loads test file corresponding to described triggered tool identification for adopting default assembly mode;
Interface debond unit, for generating test interface corresponding to described triggered tool identification loading successfully.
In embodiments of the present invention, by obtaining triggered tool identification in default testing tool catalogue, and obtain corresponding tool path, corresponding test file is obtained based on this tool path, final employing is preset assembly mode and is loaded test file, and loading the test interface generating correspondence successfully, achieve the unified management to testing tool.By adopting default testing tool catalogue, can test path corresponding to the test file of quick position testing tool, improve the search efficiency of test file, and then improve the testing efficiency to terminal applies product.
Accompanying drawing explanation
In order to be illustrated more clearly in the embodiment of the present invention or technical scheme of the prior art, be briefly described to the accompanying drawing used required in embodiment or description of the prior art below, apparently, accompanying drawing in the following describes is only some embodiments of the present invention, for those of ordinary skill in the art, under the prerequisite not paying creative work, other accompanying drawing can also be obtained according to these accompanying drawings.
Fig. 1 is the schematic flow sheet of a kind of testing tool management method that the embodiment of the present invention provides;
Fig. 2 is the schematic flow sheet of the another kind of testing tool management method that the embodiment of the present invention provides;
Fig. 3 is the example schematic of a kind of testing tool management method that the embodiment of the present invention provides;
Fig. 4 is the structural representation of a kind of user terminal that the embodiment of the present invention provides;
Fig. 5 is the structural representation of the files loading unit that the embodiment of the present invention provides;
Fig. 6 is the structural representation of the another kind of user terminal that the embodiment of the present invention provides.
Embodiment
Below in conjunction with the accompanying drawing in the embodiment of the present invention, be clearly and completely described the technical scheme in the embodiment of the present invention, obviously, described embodiment is only the present invention's part embodiment, instead of whole embodiments.Based on the embodiment in the present invention, those of ordinary skill in the art, not making the every other embodiment obtained under creative work prerequisite, belong to the scope of protection of the invention.
The testing tool management method that the embodiment of the present invention provides can be applied to the scene of testing terminal applies product, such as: user terminal obtains triggered tool identification in default testing tool catalogue, and obtain tool path corresponding to described triggered tool identification, described user terminal obtains test file corresponding to described triggered tool identification based on the tool path that described triggered tool identification is corresponding, described user terminal adopts presets test file corresponding to described the triggered tool identification of assembly mode loading, described user terminal generates the scene etc. of test interface corresponding to described triggered tool identification successfully loading.Achieve the unified management to testing tool, by adopting default testing tool catalogue, can test path corresponding to the test file of quick position testing tool, improve the search efficiency of test file, and then improve the testing efficiency to terminal applies product.
The user terminal that the embodiment of the present invention relates to can comprise: panel computer, smart mobile phone, notebook computer, palm PC, personal computer and mobile internet device (MID) etc. possess the terminal device of the test function to terminal applies product; Described terminal applies product can comprise local application (application without the need to networking), internet, applications etc. can be installed on application in mobile phone terminal or PC end.
Below in conjunction with accompanying drawing 1 and accompanying drawing 2, a kind of testing tool management method that the embodiment of the present invention provides is described in detail.
Refer to Fig. 1, for embodiments providing a kind of schematic flow sheet of testing tool management method.As shown in Figure 1, the described method of the embodiment of the present invention can comprise the following steps S101-step S104.
S101, obtains triggered tool identification in default testing tool catalogue, and obtains tool path corresponding to described triggered tool identification;
Concrete, user terminal can obtain triggered tool identification in the testing tool catalogue preset, be understandable that, one or more tool identification can be comprised in described testing tool catalogue, when there is the clicked tool identification chosen in described testing tool catalogue, determine that this clicked tool identification chosen is current triggered tool identification, described user terminal can obtain tool path corresponding to described triggered tool identification, it should be noted that, described tool identification can be the instrument title of described user terminal according to test file self-defining, numbering etc., described tool path is then the location paths at test file place under described default testing tool file, the tool path that each tool identification is all corresponding with it links in advance.
S102, obtains test file corresponding to described triggered tool identification based on the tool path that described triggered tool identification is corresponding;
Concrete, the tool path that described user terminal can be corresponding based on described triggered tool identification is searched and is obtained test file corresponding to described triggered tool identification.
S103, adopts and presets test file corresponding to described the triggered tool identification of assembly mode loading;
Concrete, described user terminal can adopt default assembly mode to load test file corresponding to described triggered tool identification, be understandable that, the file type of described test file can comprise the executable file type that instrumentation code type and suffix are .exe, therefore, in order to ensure that test file can carry out the display of test interface under unified framework, for the file type of dissimilar test file, need to adopt different default assembly modes to load test file, such as: if the test file of the instrumentation code type researched and developed voluntarily, described user terminal can adopt emission mechanism to load this test file, if the outside suffix obtained is the test file of the executable file type of .exe, described user terminal can adopt the method for Process.start () to load etc. this test file.
S104, generates test interface corresponding to described triggered tool identification loading successfully;
Concrete, load successfully at the test file that described triggered tool identification is corresponding, described user terminal can generate test interface corresponding to described triggered tool identification, preferably, for the ease of the unified management to testing tool, described user terminal can be corresponding at described triggered tool identification test file load successfully, adopt the form of subwindow to generate test interface corresponding to described triggered tool identification.By the form of subwindow, test interface being shown, without the need to frequently switching the test interface of testing tool in system platform, the testing efficiency to terminal applies product can be improved further.
In embodiments of the present invention, by obtaining triggered tool identification in default testing tool catalogue, and obtain corresponding tool path, corresponding test file is obtained based on this tool path, final employing is preset assembly mode and is loaded test file, and loading the test interface generating correspondence successfully, achieve the unified management to testing tool.By adopting default testing tool catalogue, can test path corresponding to the test file of quick position testing tool, improve the search efficiency of test file, and then improve the testing efficiency to terminal applies product.
Refer to Fig. 2, for embodiments providing the schematic flow sheet of another kind of testing tool management method.As shown in Figure 2, the described method of the embodiment of the present invention can comprise the following steps S201-step S212.
S201, obtains at least one test file be stored in advance in default testing tool file;
S202, generates tool path and tool identification that at least one test file described, each test file is corresponding, and stores tool path corresponding to described each test file and tool identification;
S203, the tool identification corresponding according to described each test file arranges testing tool catalogue;
Concrete, user terminal can obtain at least one test file be stored in advance in default testing tool file, preferably, the test file of the testing tool of dispersion can move to respectively in default testing tool file by tester in described user terminal, described user terminal can generate the tool path and tool identification that at least one test file described, each test file is corresponding respectively, described tool identification can be the instrument title of described user terminal according to test file self-defining, numbering etc., described tool path is then the location paths at test file place under described default testing tool file, described user terminal can store tool path corresponding to described each test file and tool identification respectively, the tool identification that described user terminal is corresponding according to described each test file further arranges testing tool catalogue, preferably, tool identification in described testing tool catalogue adopts the mode of tree-shaped list to arrange.
Please also refer to Fig. 3, for embodiments providing a kind of example schematic of testing tool management method.As shown in Figure 3, described user terminal can load catalogue file corresponding to described testing tool catalogue, can the testing tool catalogue of interface display to generate, as the testing tool catalogue in left side in Fig. 3, the testing tool set of three types can be comprised in this testing tool catalogue, as common test instrument (all spendable testing tool of terminal applies product of mobile phone terminal and PC end), mobile phone test instrument, PC testing tool etc., tool identification corresponding to respective one or more testing tools can be recorded respectively in the testing tool set of every type, such as: the tool identification that can comprise account management device in the set of common test instrument, the tool identification of automated debug and the tool identification etc. arranged of growing up.
S204, obtains triggered tool identification in default testing tool catalogue;
Concrete, described user terminal can obtain triggered tool identification in the testing tool catalogue preset, be understandable that, one or more tool identification can be comprised in described testing tool catalogue, when there is the clicked tool identification chosen in described testing tool catalogue, determine that this clicked tool identification chosen is current triggered tool identification.
S205, judges currently whether there is test interface corresponding to described triggered tool identification based on described triggered tool identification;
Concrete, described user terminal is after getting described triggered tool identification, first can judge currently whether there is test interface corresponding to described triggered tool identification based on described triggered tool identification, namely judge whether the test interface that current triggered tool identification is corresponding is unlocked, if so, then proceed to and perform step S206; If not, then execution step S207 is proceeded to.
S206, switches to the test interface that described triggered tool identification is corresponding;
Concrete, if there is test interface corresponding to described triggered tool identification based on described triggered tool identification, then described user terminal can be directly switch into the subwindow at test interface place corresponding to described triggered tool identification.
As shown in Figure 3, if the tool identification triggered got current is the tool identification of Monkey testing tool, and the test interface that the current tool identification that there is Monkey testing tool is corresponding, then described user terminal is directly switch into the subwindow at test interface place corresponding to the tool identification of Monkey testing tool, simultaneously, the tool identification of the Monkey testing tool at selection card place can highlight, and has represented the test interface corresponding for the tool identification of Monkey testing tool of current display.
S207, obtains the tool path that described triggered tool identification is corresponding;
Concrete, if there is not test interface corresponding to described triggered tool identification based on described triggered tool identification, then described user terminal can obtain tool path corresponding to described triggered tool identification.
S208, obtains test file corresponding to described triggered tool identification based on the tool path that described triggered tool identification is corresponding;
Concrete, the tool path that described user terminal can be corresponding based on described triggered tool identification is searched and is obtained test file corresponding to described triggered tool identification.
S209, detects the file type of test file corresponding to described triggered tool identification;
S210, when detecting that described file type is instrumentation code type, adopts reflex mechanism to load test file corresponding to described triggered tool identification;
S211, when detecting that described file type be suffix is the executable file type of .exe, adopts the method for Process.start () to load test file corresponding to described triggered tool identification;
Concrete, described user terminal can detect the file type of test file corresponding to described triggered tool identification, be understandable that, the file type of described test file can comprise the executable file type that instrumentation code type and suffix are .exe, when detecting that described file type is instrumentation code type, described user terminal adopts reflex mechanism to load test file corresponding to described triggered tool identification, when detecting that described file type be suffix is the executable file type of .exe, described user terminal adopts the method for Process.start () to load test file corresponding to described triggered tool identification.Wherein, described reflex mechanism refers to that a kind of ability of itself state or behavior can be accessed, detects and be revised to program, the method of described Process.start () refers to the process resource that Start (info) attribute of startup (or reusing) this Process assembly is specified, and by the method for itself and this component liaison.
S212, generates test interface corresponding to described triggered tool identification loading successfully.
Concrete, load successfully at the test file that described triggered tool identification is corresponding, described user terminal can generate test interface corresponding to described triggered tool identification, preferably, for the ease of the unified management to testing tool, described user terminal can be corresponding at described triggered tool identification test file load successfully, adopt the form of subwindow to generate test interface corresponding to described triggered tool identification.By the form of subwindow, test interface being shown, without the need to frequently switching the test interface of testing tool in system platform, the testing efficiency to terminal applies product can be improved further.
As shown in Figure 3, if the tool identification triggered got current is the tool identification of Monkey testing tool, described user terminal can generate test interface corresponding to the tool identification of described Monkey testing tool with the form of subwindow, such as: can comprise that Monkey tests most basic option, Monkey tests scaling option and test time show for the Monkey test showing test process.
In embodiments of the present invention, by obtaining triggered tool identification in default testing tool catalogue, and obtain corresponding tool path, corresponding test file is obtained based on this tool path, final employing is preset assembly mode and is loaded test file, and loading the test interface generating correspondence successfully, achieve the unified management to testing tool.By adopting default testing tool catalogue, can test path corresponding to the test file of quick position testing tool, improve the search efficiency of test file, and then improve the testing efficiency to terminal applies product; For the file type of dissimilar test file, by adopting different default assembly modes to load test file, ensure that the diversity can supporting the testing tool loaded; The form of subwindow is adopted to generate test interface corresponding to described triggered tool identification.By the form of subwindow, test interface being shown, without the need to frequently switching the test interface of testing tool in system platform, the testing efficiency to terminal applies product can be improved further.
Below in conjunction with accompanying drawing 4-accompanying drawing 6, the user terminal that the embodiment of the present invention provides is described in detail.It should be noted that, the user terminal shown in accompanying drawing 4-accompanying drawing 6, for performing Fig. 1 of the present invention and method embodiment illustrated in fig. 2, for convenience of explanation, illustrate only the part relevant to the embodiment of the present invention, concrete ins and outs do not disclose, and please refer to the embodiment shown in Fig. 1 and Fig. 2 of the present invention.
Refer to Fig. 4, for embodiments providing a kind of structural representation of user terminal.As shown in Figure 4, the described user terminal 1 of the embodiment of the present invention can comprise: path acquiring unit 11, first file obtaining unit 12, files loading unit 13 and Interface debond unit 14.
Path acquiring unit 11, for obtaining triggered tool identification in default testing tool catalogue, and obtains tool path corresponding to described triggered tool identification;
In specific implementation, described path acquiring unit 11 can obtain triggered tool identification in the testing tool catalogue preset, be understandable that, one or more tool identification can be comprised in described testing tool catalogue, when there is the clicked tool identification chosen in described testing tool catalogue, determine that this clicked tool identification chosen is current triggered tool identification, described path acquiring unit 11 can obtain tool path corresponding to described triggered tool identification, it should be noted that, described tool identification can be the instrument title of described user terminal 1 according to test file self-defining, numbering etc., described tool path is then the location paths at test file place under described default testing tool file, the tool path that each tool identification is all corresponding with it links in advance.
First file obtaining unit 12, obtains test file corresponding to described triggered tool identification for the tool path corresponding based on described triggered tool identification;
In specific implementation, the tool path that described first file obtaining unit 12 can be corresponding based on described triggered tool identification is searched and is obtained test file corresponding to described triggered tool identification.
Files loading unit 13, loads test file corresponding to described triggered tool identification for adopting default assembly mode;
In specific implementation, described files loading unit 13 can adopt default assembly mode to load test file corresponding to described triggered tool identification, be understandable that, the file type of described test file can comprise the executable file type that instrumentation code type and suffix are .exe, therefore, in order to ensure that test file can carry out the display of test interface under unified framework, for the file type of dissimilar test file, need to adopt different default assembly modes to load test file, such as: if the test file of the instrumentation code type researched and developed voluntarily, described files loading unit 13 can adopt emission mechanism to load this test file, if the outside suffix obtained is the test file of the executable file type of .exe, described files loading unit 13 can adopt the method for Process.start () to load etc. this test file.
Concrete, please also refer to Fig. 5, for embodiments providing the structural representation of files loading unit.As shown in Figure 5, described files loading unit 13 can comprise:
Type detection subelement 131, for detecting the file type of test file corresponding to described triggered tool identification;
Files loading subelement 132, for when detecting that described file type is instrumentation code type, adopts reflex mechanism to load test file corresponding to described triggered tool identification;
Files loading subelement 132, also for when detecting that described file type be suffix is the executable file type of .exe, adopts the method for Process.start () to load test file corresponding to described triggered tool identification;
In specific implementation, described type detection subelement 131 can detect the file type of test file corresponding to described triggered tool identification, be understandable that, the file type of described test file can comprise the executable file type that instrumentation code type and suffix are .exe, when detecting that described file type is instrumentation code type, described files loading subelement 132 adopts reflex mechanism to load test file corresponding to described triggered tool identification, when detecting that described file type be suffix is the executable file type of .exe, described files loading subelement 132 adopts the method for Process.start () to load test file corresponding to described triggered tool identification.Wherein, described reflex mechanism refers to that a kind of ability of itself state or behavior can be accessed, detects and be revised to program, the method of described Process.start () refers to the process resource that Start (info) attribute of startup (or reusing) this Process assembly is specified, and by the method for itself and this component liaison.
Interface debond unit 14, for generating test interface corresponding to described triggered tool identification loading successfully;
In specific implementation, load successfully at the test file that described triggered tool identification is corresponding, described Interface debond unit 14 can generate test interface corresponding to described triggered tool identification, preferably, for the ease of the unified management to testing tool, described Interface debond unit 14 can be corresponding at described triggered tool identification test file load successfully, adopt the form of subwindow to generate test interface corresponding to described triggered tool identification.By the form of subwindow, test interface being shown, without the need to frequently switching the test interface of testing tool in system platform, the testing efficiency to terminal applies product can be improved further.
In embodiments of the present invention, by obtaining triggered tool identification in default testing tool catalogue, and obtain corresponding tool path, corresponding test file is obtained based on this tool path, final employing is preset assembly mode and is loaded test file, and loading the test interface generating correspondence successfully, achieve the unified management to testing tool.By adopting default testing tool catalogue, can test path corresponding to the test file of quick position testing tool, improve the search efficiency of test file, and then improve the testing efficiency to terminal applies product; For the file type of dissimilar test file, by adopting different default assembly modes to load test file, ensure that the diversity can supporting the testing tool loaded.
Refer to Fig. 6, for embodiments providing the structural representation of another kind of mobile terminal.As shown in Figure 6, the described mobile terminal 1 of the embodiment of the present invention can comprise: path acquiring unit 11, first file obtaining unit 12, files loading unit 13, Interface debond unit 14, second file obtaining unit 15, information memory cell 16, catalogue setting unit 17, judging unit 18, changing interface unit 19 and notification unit 20; Wherein, the structure of path acquiring unit 11, first file obtaining unit 12, files loading unit 13 and Interface debond unit 14 can the specific descriptions of embodiment shown in Figure 4, do not repeat at this.
Second file obtaining unit 15, for obtaining at least one test file be stored in advance in default testing tool file;
Information memory cell 16, for generating the tool path and tool identification that at least one test file described, each test file is corresponding, and stores tool path corresponding to described each test file and tool identification;
Catalogue setting unit 17, arranges testing tool catalogue for the tool identification corresponding according to described each test file;
In specific implementation, described second file obtaining unit 15 can obtain at least one test file be stored in advance in default testing tool file, preferably, the test file of the testing tool of dispersion can move to respectively in default testing tool file by tester in described user terminal 1, described information memory cell 16 can generate the tool path and tool identification that at least one test file described, each test file is corresponding respectively, described tool identification can be the instrument title of described user terminal 1 according to test file self-defining, numbering etc., described tool path is then the location paths at test file place under described default testing tool file, described information memory cell 16 can store tool path corresponding to described each test file and tool identification respectively, the tool identification that described catalogue setting unit 17 is corresponding according to described each test file further arranges testing tool catalogue, preferably, tool identification in described testing tool catalogue adopts the mode of tree-shaped list to arrange.
Whether judging unit 18, currently exist test interface corresponding to described triggered tool identification for judging based on described triggered tool identification;
In specific implementation, described judging unit 18 is after getting described triggered tool identification, first can judge currently whether there is test interface corresponding to described triggered tool identification based on described triggered tool identification, namely judge whether the test interface that current triggered tool identification is corresponding is unlocked.
Changing interface unit 19, if judge that the current judged result that whether there is test interface corresponding to described triggered tool identification is yes for described judging unit 18, then switches to the test interface that described triggered tool identification is corresponding;
In specific implementation, if described judging unit 18 judges that the current judged result that whether there is test interface corresponding to described triggered tool identification is yes, then described changing interface unit 19 can be directly switch into the subwindow at test interface place corresponding to described triggered tool identification.
Notification unit 20, if judge that the current judged result that whether there is test interface corresponding to described triggered tool identification is no for described judging unit 18, then notify that described path acquiring unit 11 performs and obtain tool path corresponding to described triggered tool identification;
In specific implementation, if described judging unit 18 judges that the current judged result that whether there is test interface corresponding to described triggered tool identification is no, then described notification unit 20 can notify that described path acquiring unit 11 performs and obtain tool path corresponding to described triggered tool identification.
In embodiments of the present invention, by obtaining triggered tool identification in default testing tool catalogue, and obtain corresponding tool path, corresponding test file is obtained based on this tool path, final employing is preset assembly mode and is loaded test file, and loading the test interface generating correspondence successfully, achieve the unified management to testing tool.By adopting default testing tool catalogue, can test path corresponding to the test file of quick position testing tool, improve the search efficiency of test file, and then improve the testing efficiency to terminal applies product; For the file type of dissimilar test file, by adopting different default assembly modes to load test file, ensure that the diversity can supporting the testing tool loaded; The form of subwindow is adopted to generate test interface corresponding to described triggered tool identification.By the form of subwindow, test interface being shown, without the need to frequently switching the test interface of testing tool in system platform, the testing efficiency to terminal applies product can be improved further.
One of ordinary skill in the art will appreciate that all or part of flow process realized in above-described embodiment method, that the hardware that can carry out instruction relevant by computer program has come, described program can be stored in a computer read/write memory medium, this program, when performing, can comprise the flow process of the embodiment as above-mentioned each side method.Wherein, described storage medium can be magnetic disc, CD, read-only store-memory body (Read-OnlyMemory, ROM) or random store-memory body (RandomAccessMemory, RAM) etc.
Above disclosedly be only present pre-ferred embodiments, certainly can not limit the interest field of the present invention with this, therefore according to the equivalent variations that the claims in the present invention are done, still belong to the scope that the present invention is contained.
Claims (10)
1. a testing tool management method, is characterized in that, comprising:
In default testing tool catalogue, obtain triggered tool identification, and obtain tool path corresponding to described triggered tool identification;
Test file corresponding to described triggered tool identification is obtained based on the tool path that described triggered tool identification is corresponding;
Adopt and preset test file corresponding to described the triggered tool identification of assembly mode loading;
Generate test interface corresponding to described triggered tool identification loading successfully.
2. method according to claim 1, is characterized in that, described in default testing tool catalogue, obtain triggered tool identification before, also comprise:
Obtain at least one test file be stored in advance in default testing tool file;
Generate tool path and tool identification that at least one test file described, each test file is corresponding, and store tool path corresponding to described each test file and tool identification;
The tool identification corresponding according to described each test file arranges testing tool catalogue.
3. method according to claim 1, is characterized in that, before the tool path that the tool identification that described acquisition is described triggered is corresponding, also comprises:
Judge currently whether there is test interface corresponding to described triggered tool identification based on described triggered tool identification;
If so, test interface corresponding to described triggered tool identification is then switched to;
If not, then the step obtaining tool path corresponding to described triggered tool identification is performed.
4. method according to claim 1, is characterized in that, described employing is preset assembly mode and loaded test file corresponding to described triggered tool identification, comprising:
Detect the file type of test file corresponding to described triggered tool identification;
When detecting that described file type is instrumentation code type, reflex mechanism is adopted to load test file corresponding to described triggered tool identification;
When detecting that described file type be suffix is the executable file type of .exe, the method for Process.start () is adopted to load test file corresponding to described triggered tool identification.
5. method according to claim 1, is characterized in that, describedly generates test interface corresponding to described triggered tool identification loading successfully, comprising:
Test interface corresponding to described triggered tool identification is generated at the form loading employing subwindow successfully.
6. a user terminal, is characterized in that, comprising:
Path acquiring unit, for obtaining triggered tool identification in default testing tool catalogue, and obtains tool path corresponding to described triggered tool identification;
First file obtaining unit, obtains test file corresponding to described triggered tool identification for the tool path corresponding based on described triggered tool identification;
Files loading unit, loads test file corresponding to described triggered tool identification for adopting default assembly mode;
Interface debond unit, for generating test interface corresponding to described triggered tool identification loading successfully.
7. terminal according to claim 6, is characterized in that, also comprises:
Second file obtaining unit, for obtaining at least one test file be stored in advance in default testing tool file;
Information memory cell, for generating the tool path and tool identification that at least one test file described, each test file is corresponding, and stores tool path corresponding to described each test file and tool identification;
Catalogue setting unit, arranges testing tool catalogue for the tool identification corresponding according to described each test file.
8. terminal according to claim 6, is characterized in that, also comprises:
Whether judging unit, currently exist test interface corresponding to described triggered tool identification for judging based on described triggered tool identification;
Changing interface unit, if judge that the current judged result that whether there is test interface corresponding to described triggered tool identification is yes for described judging unit, then switches to the test interface that described triggered tool identification is corresponding;
Notification unit, if judge that the current judged result that whether there is test interface corresponding to described triggered tool identification is no for described judging unit, then notifies that described path acquiring unit performs and obtains tool path corresponding to described triggered tool identification.
9. terminal according to claim 6, is characterized in that, described files loading unit comprises:
Type detection subelement, for detecting the file type of test file corresponding to described triggered tool identification;
Files loading subelement, for when detecting that described file type is instrumentation code type, adopts reflex mechanism to load test file corresponding to described triggered tool identification;
Files loading subelement, also for when detecting that described file type be suffix is the executable file type of .exe, adopts the method for Process.start () to load test file corresponding to described triggered tool identification.
10. terminal according to claim 6, is characterized in that, described Interface debond unit is specifically for generating test interface corresponding to described triggered tool identification at the form loading employing subwindow successfully.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510874109.2A CN105487979A (en) | 2015-12-02 | 2015-12-02 | Test tool management method and user terminal |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510874109.2A CN105487979A (en) | 2015-12-02 | 2015-12-02 | Test tool management method and user terminal |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN105487979A true CN105487979A (en) | 2016-04-13 |
Family
ID=55674971
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201510874109.2A Pending CN105487979A (en) | 2015-12-02 | 2015-12-02 | Test tool management method and user terminal |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN105487979A (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109116129A (en) * | 2017-06-26 | 2019-01-01 | 深圳回收宝科技有限公司 | Endpoint detection methods, detection device, system and storage medium |
| CN109144799A (en) * | 2018-08-14 | 2019-01-04 | 深圳壹账通智能科技有限公司 | Integrated testing method, apparatus, computer equipment and storage medium |
| CN109726104A (en) * | 2018-05-15 | 2019-05-07 | 平安普惠企业管理有限公司 | Test bag generation method, test terminal and the storage medium of mobile terminal |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1369787A (en) * | 2001-02-14 | 2002-09-18 | 英业达股份有限公司 | Test tool loading and managing method for test system |
| CN101174240A (en) * | 2006-11-03 | 2008-05-07 | 凌阳科技股份有限公司 | Software testing management method and system thereof |
| CN102495789A (en) * | 2011-10-18 | 2012-06-13 | 瑞斯康达科技发展股份有限公司 | Automatic test method and device for the same |
| US20140289689A1 (en) * | 2013-03-25 | 2014-09-25 | Fujitsu Limited | Wiring inspection apparatus and wiring inspection method |
| CN104331358A (en) * | 2014-10-30 | 2015-02-04 | 上海斐讯数据通信技术有限公司 | Test management system and method |
-
2015
- 2015-12-02 CN CN201510874109.2A patent/CN105487979A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1369787A (en) * | 2001-02-14 | 2002-09-18 | 英业达股份有限公司 | Test tool loading and managing method for test system |
| CN101174240A (en) * | 2006-11-03 | 2008-05-07 | 凌阳科技股份有限公司 | Software testing management method and system thereof |
| CN102495789A (en) * | 2011-10-18 | 2012-06-13 | 瑞斯康达科技发展股份有限公司 | Automatic test method and device for the same |
| US20140289689A1 (en) * | 2013-03-25 | 2014-09-25 | Fujitsu Limited | Wiring inspection apparatus and wiring inspection method |
| CN104331358A (en) * | 2014-10-30 | 2015-02-04 | 上海斐讯数据通信技术有限公司 | Test management system and method |
Non-Patent Citations (4)
| Title |
|---|
| (美)HERBERT SCHILDT: "《C#2.0完全参考手册》", 30 September 2007, 北京：清华大学出版社 * |
| 周清平: "《.Net项目开发实践》", 31 May 2015, 长沙：中南大学出版社 * |
| 李千目: "《软件自动化测试原理与实证》", 31 August 2015, 北京：清华大学出版社 * |
| 赵川等: "基于Eclipse的测试工具管理平台构建", 《计算机工程》 * |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109116129A (en) * | 2017-06-26 | 2019-01-01 | 深圳回收宝科技有限公司 | Endpoint detection methods, detection device, system and storage medium |
| CN109726104A (en) * | 2018-05-15 | 2019-05-07 | 平安普惠企业管理有限公司 | Test bag generation method, test terminal and the storage medium of mobile terminal |
| CN109726104B (en) * | 2018-05-15 | 2024-02-27 | 深圳市兴海物联科技有限公司 | Test packet generation method of mobile terminal, test terminal and storage medium |
| CN109144799A (en) * | 2018-08-14 | 2019-01-04 | 深圳壹账通智能科技有限公司 | Integrated testing method, apparatus, computer equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP2625791B1 (en) | Apparatus and method for adaptive gesture recognition in portable terminal | |
| CN102446104B (en) | The method starting computer system | |
| CN106844028B (en) | System switching method based on dual systems and mobile terminal | |
| CN105487979A (en) | Test tool management method and user terminal | |
| CN111506318A (en) | Circuit board chip burning method, device, terminal and computer readable storage medium | |
| CN103714069A (en) | Method and device for opening pages in background | |
| CN104536863A (en) | Application program test method and device | |
| JP2011129028A (en) | Test support device for optimizing test scenario to minimize total test time, test device, test support method, and computer program | |
| CN108255509B (en) | Application deployment method, device, equipment and readable storage medium | |
| CN105677148A (en) | Terminal application searching method and device | |
| CN107908679B (en) | Script statement conversion method and device and computer readable storage medium | |
| CN109684213B (en) | Test method, test device and storage medium | |
| CN105357378A (en) | Method and mobile terminal for automatically opening WIFI (Wireless Fidelity) list and connecting WIFI | |
| CN104915228A (en) | Application program language setting method and device | |
| CN103024928A (en) | Terminal wireless connection method and wireless terminal | |
| CN103914212A (en) | Terminal device and application configuration method thereof | |
| CN106980402B (en) | Method and device for judging reset calibration and terminal | |
| CN106897222A (en) | TP firmwares changing method and device | |
| CN103294617A (en) | Method for expanding device drivers of electronic device and portable intelligent electronic device | |
| CN114489495A (en) | Data storage method and device, terminal equipment and storage medium | |
| CN104503881A (en) | Handheld device power consumption detecting method and device and handheld device | |
| CN104317645A (en) | Method and device of monitoring port by virtue of application program embodiment | |
| CN111563008A (en) | Data storage method, device, storage system and computer readable storage medium | |
| CN110908701B (en) | Firmware version switching method and device, storage medium and electronic equipment | |
| CN101847074A (en) | Array functional arrangements, application system and method |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20160413 |