Move Copy/Paste actions to DB queue

Jetzt loslegen. Gratis!
oder registrieren mit Ihrer E-Mail-Adresse
Move Copy/Paste actions to DB queue von Mind Map: Move Copy/Paste actions to DB queue

1. Test Execution

1.1. Data

1.1.1. Atifact

1.1.1.1. Test cycle

1.1.1.1.1. 1 test cycle

1.1.1.1.2. n test cycle

1.1.1.2. Test suite

1.1.1.2.1. number or test suite

1.1.1.2.2. test suite fields

1.1.1.3. Test run

1.1.1.3.1. number of test run

1.1.1.3.2. test run type

1.1.1.3.3. test run fields

1.1.2. destination test container

1.1.2.1. copy test cycle to

1.1.2.1.1. Root

1.1.2.1.2. Release

1.1.2.1.3. test cycle

1.1.2.2. copy test suite to

1.1.2.2.1. Root

1.1.2.2.2. Release

1.1.2.2.3. test cycle

1.1.2.3. copy test run to

1.1.2.3.1. Root

1.1.2.3.2. Release

1.1.2.3.3. test cycle

1.1.2.3.4. test suite

1.1.3. user permission

1.1.3.1. with Create test run/ Test Suite / Test Cycle permission

1.2. Function

1.2.1. copy 1 artifact to destination test container

1.2.1.1. Add record to BD queue

1.2.1.1.1. Sample: copy 1 test cycle, each test cycle has 0/1/n sub test cycle, test suite, test run

1.2.1.2. After copy process is completed

1.2.1.2.1. Show message: [1 Test cycle/ Test Suite/ Test Run] has been copied to [destination container name] successfully

1.2.1.2.2. Show notification on Bell

1.2.1.2.3. New Test cycle/ Test suite/ Test run is shown in destination container with correct information: name, properties

1.2.2. copy n artifact to destination test container

1.2.2.1. Add record to BD queue

1.2.2.1.1. Sample: copy 3 test cycle, each test cycle has 0/1/n sub test cycle, test suite, test run

1.2.2.2. After copy process is completed

1.2.2.2.1. Show message: [n Test cycle/ Test Suite/ Test Run] has been copied to [destination container name] successfully

1.2.2.2.2. Show notification on Bell

1.2.2.2.3. New Test cycle/ Test suite/ Test run is shown in destination container with correct information: name, properties

1.2.2.2.4. structure maybe changed

1.2.2.3. number of test runs

1.2.2.3.1. <= 20 test runs

1.2.2.3.2. > 20 test runs or copy include test cycle/ test suite

1.2.3. Process bar

1.2.3.1. Click "Continue working" button

1.2.3.1.1. Process bar is closed

1.2.3.1.2. the system allows users to continue working

1.2.3.1.3. When copying process is completed:

1.2.3.2. do not click on "Continue working" button

1.2.3.2.1. Process bar is still shown

1.2.3.2.2. User cannot continue working

1.2.3.2.3. When copying process is completed:

1.3. Time

1.3.1. define in load test

1.4. Interface

1.4.1. UI

1.5. Operation

1.6. Framework

1.7. Structure

2. Test Design

2.1. Data

2.1.1. Atifact

2.1.1.1. Module

2.1.1.1.1. number or module

2.1.1.2. Test case

2.1.1.2.1. number of test case

2.1.1.2.2. test case type

2.1.1.2.3. test case fields

2.1.2. destination container

2.1.2.1. copy module to

2.1.2.1.1. current project

2.1.2.1.2. cross project

2.1.2.2. copy test case to

2.1.2.2.1. current project

2.1.2.2.2. cross project

2.1.3. user permission

2.1.3.1. with Create module test case permission

2.2. Function

2.2.1. copy 1 artifact to destination container

2.2.1.1. Add record to BD queue

2.2.1.1.1. Sample: copy module, each module has 0/1/n sub module/ test case

2.2.1.2. After copy process is completed

2.2.1.2.1. Show message: [1 Module/ Test case] has been copied to [destination container name] successfully

2.2.1.2.2. Show notification on Bell

2.2.1.2.3. New Module/ Test case is shown in destination container with correct information: name, properties

2.2.1.2.4. Only copy Module and Test case, do not copy requirements

2.2.2. copy n artifact to destination test container

2.2.2.1. Add record to BD queue

2.2.2.1.1. Sample: copy 3 module, each module has 0/1/n sub module/ test case

2.2.2.2. After copy process is completed

2.2.2.2.1. Show message: [n Module/Test case] has been copied to [destination container name] successfully

2.2.2.2.2. Show notification on Bell

2.2.2.2.3. New Module/ Test case is shown in destination container with correct information: name, properties

2.2.2.2.4. structure maybe changed

2.2.2.2.5. Only copy Module and Test case, do not copy requirements

2.2.2.3. number of test cases

2.2.2.3.1. <= 20 test cases

2.2.2.3.2. > 20 test cases or copy include module

2.2.3. Process bar

2.2.3.1. Click "Continue working" button

2.2.3.1.1. Process bar is closed

2.2.3.1.2. the system allows users to continue working

2.2.3.1.3. When copying process is completed:

2.2.3.2. do not click on "Continue working" button

2.2.3.2.1. Process bar is still shown

2.2.3.2.2. User cannot continue working

2.2.3.2.3. When copying process is completed:

2.3. Time

2.3.1. define in load test

2.4. Interface

2.4.1. UI

2.5. Operation

2.6. Framework

2.7. Structure

3. Requirement

3.1. Data

3.1.1. Atifact

3.1.1.1. Module

3.1.1.1.1. number or module

3.1.1.2. requirement

3.1.1.2.1. number of requirement

3.1.1.2.2. requirement type

3.1.1.2.3. requirement fields

3.1.2. destination container

3.1.2.1. copy module to

3.1.2.1.1. Root

3.1.2.1.2. module

3.1.2.1.3. parent module to sub module

3.1.2.2. copy requirement to

3.1.2.2.1. Root

3.1.2.2.2. module

3.1.3. user permission

3.1.3.1. with Create module/ requirement permission

3.2. Function

3.2.1. copy 1 artifact to destination container

3.2.1.1. Add record to BD queue

3.2.1.1.1. Sample: copy module, each module has 0/1/n sub module/ requirement

3.2.1.2. After copy process is completed

3.2.1.2.1. Show message: [1 Module/ Test requirement] has been copied to [destination container name] successfully

3.2.1.2.2. Show notification on Bell

3.2.1.2.3. New Module/ Requirement is shown in destination container with correct information: name, properties

3.2.1.2.4. Only copy Module and Requirement, do not copy test case

3.2.2. copy n artifact to destination test container

3.2.2.1. Add record to BD queue

3.2.2.1.1. Sample: copy 3 module, each module has 0/1/n sub module/ requirement

3.2.2.2. After copy process is completed

3.2.2.2.1. Show message: [n Module/Test case] has been copied to [destination container name] successfully

3.2.2.2.2. Show notification on Bell

3.2.2.2.3. New Module/ Test case is shown in destination container with correct information: name, properties

3.2.2.2.4. structure maybe changed

3.2.2.2.5. Only copy Module and Requirement, do not copy test case

3.2.2.3. number of requirements

3.2.2.3.1. <= 20 requirements

3.2.2.3.2. > 20 requirements or copy include module

3.2.3. Process bar

3.2.3.1. Click "Continue working" button

3.2.3.1.1. Process bar is closed

3.2.3.1.2. the system allows users to continue working

3.2.3.1.3. When copying process is completed:

3.2.3.2. do not click on "Continue working" button

3.2.3.2.1. Process bar is still shown

3.2.3.2.2. User cannot continue working

3.2.3.2.3. When copying process is completed:

3.3. Time

3.3.1. define in load test

3.4. Interface

3.4.1. UI

3.5. Operation

3.6. Framework

3.7. Structure