Skip to main content
summaryrefslogtreecommitdiffstats
blob: 6ab1b067e9716db9872e3c0acc66c6452a3f98b5 (plain) (blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
<?xml version="1.0" encoding="UTF-8"?>
<!-- 
  Copyright (c) 2014 BREDEX GmbH.
  All rights reserved. This program and the accompanying materials
  are made available under the terms of the Eclipse Public License v1.0
  which accompanies this distribution, and is available at
  http://www.eclipse.org/legal/epl-v10.html
-->

<section xml:id="saving-test-cases-from-an-editor-as-a-new-test-case" version="5.0" xmlns="http://docbook.org/ns/docbook"
                                                                                 xmlns:xi="http://www.w3.org/2001/XInclude"
                                                                                 xmlns:xl="http://www.w3.org/1999/xlink" >
  <title>Saving Test Cases from an editor as a new Test Case</title>
  <anchor role="helpid" condition="guidancerSpecTestCaseEditorContextId" xml:id="saving-test-cases-from-an-editor-as-a-new-test-case.guidancerSpecTestCaseEditorContextId" xreflabel="Test Case Editor"/>
  <anchor role="helpid" condition="testSuiteEditorContextId" xml:id="saving-test-cases-from-an-editor-as-a-new-test-case.testSuiteEditorContextId" xreflabel="Test Suite Editor"/>
  <para>
    You can save selected Test Cases from other Test Cases and from
    Test Suites. This lets you create a new keyword that contains
    the selected modules without having to manually find them and
    reuse them.
  </para>
  <orderedlist>
    <listitem>
      <para>
        Open the Test Case Editor or Test Suite Editor by
        double-clicking on the Test Case or Test Suite you want to
        edit.
      </para>
    </listitem>
    <listitem>
      <para>
        Select the Test Cases you want to save into the new Test
        Case by single-clicking them. Use
        <emphasis role="input">»CTRL«</emphasis> to select more than one
        item.
      </para>
    </listitem>
    <listitem>
      <para>
        Right-click in the editor and select:
      </para>
        
      <para>
        <emphasis role="menuPath">Refactor</emphasis>--&gt;<emphasis role="menuPath">Save as new...</emphasis>.
      </para>
    </listitem>
    <listitem>
      <para>
        When prompted, enter a name for the new Test Case.
      </para>
    </listitem>
    <listitem>
      <para>
        A new Test Case will be created containing the Test Cases
        you selected, with the data and component names they used in
        the current editor.
      </para>
    </listitem>
    <listitem>
      <para>
        The Test Case you just created is visible in the Test Case
        Browser.
      </para>
    </listitem>
  </orderedlist>
  <para role="warning">
    Use this feature if you have created reusable Test Cases
    that are correctly modularized, but you require them again (e.g.
    prerequisites for another Test Case). If the sequence of actions
    you require is a recurring logical sequence (e.g. enter
    username, enter password, then click OK for a login dialog),
    then we strongly recommend using the
    <emphasis>Extract</emphasis> function
    (<xref linkend="extracting-test-cases-from-editors-refactoring"/>) instead. This will give you one
    reusable module, and therefore one central place to make any
    changes should this sequence change.
  </para>
</section>

Back to the top