docs: Update en test docs
Update en test docs Change-Id: I1d66ff584fea3ffb312e000d46d8481eee623227
This commit is contained in:
wuduochao
hanxiang gao
parent
2cd9913674
commit
63ef5d01e3
@ -58,7 +58,7 @@ E2E test environment has been successfully built in Centos and wsl2 of Windows
|
||||
- E2E configuration files are stored in `test/e2e/config/config.yaml`, Configured in it:
|
||||
- `baseUrl`, test access path
|
||||
- `env`, environment variable
|
||||
- `switchToAdminProject`, Do you need to switch to the `admin` project after logging in
|
||||
- `switchToAdminProject`, Switch to the `admin` project after logging in
|
||||
- `username`, User name to access the console, a user with console operation permissions is required
|
||||
- `password`, Password to access the console
|
||||
- `usernameAdmin`, The user name to access the management platform, a user with the operation authority of the management platform is required
|
||||
|
||||
@ -11,7 +11,7 @@ test
|
||||
│ │ ├── metadata.json (Test metadata read file)
|
||||
│ │ ├── stack-content.yaml (Files read by the test stack)
|
||||
│ │ └── stack-params.yaml (Files read by the test stack)
|
||||
│ ├── integration (Storage unit test)
|
||||
│ ├── integration (Store unit test)
|
||||
│ │ └── pages (Adjust the directory according to the webpage menu structure)
|
||||
│ │ ├── compute (compute)
|
||||
│ │ │ ├── aggregate.spec.js (aggregate)
|
||||
@ -53,7 +53,7 @@ test
|
||||
│ │ ├── qos.spec.js (QoS)
|
||||
│ │ ├── snapshot.spec.js (Volume snapshot)
|
||||
│ │ ├── storage.spec.js (Storage)
|
||||
│ │ ├── volume-type.spec.js (Volume tyoe)
|
||||
│ │ ├── volume-type.spec.js (Volume type)
|
||||
│ │ └── volume.spec.js (Volume)
|
||||
│ ├── plugins (Cypress plugins)
|
||||
│ │ └── index.js (Configured to read the configuration file, configured to use the code coverage function)
|
||||
@ -63,18 +63,18 @@ test
|
||||
│ ├── results (Store test result files)
|
||||
│ ├── screenshots (Store a snapshot of the test error)
|
||||
│ ├── support (When writing a test case, double-wrapped function)
|
||||
│ │ ├── commands.js (Storage login, logout and other operation functions)
|
||||
│ │ ├── common.js (Storage base functions)
|
||||
│ │ ├── constants.js (Storage the route of each resource)
|
||||
│ │ ├── detail-commands.js (Storage the functions related to the resource detail page, based on the framework, the operation of the detail page is consistent)
|
||||
│ │ ├── commands.js (Store login, logout and other operation functions)
|
||||
│ │ ├── common.js (Store base functions)
|
||||
│ │ ├── constants.js (Store the route of each resource)
|
||||
│ │ ├── detail-commands.js (Store the functions related to the resource detail page, based on the framework, the operation of the detail page is consistent)
|
||||
│ │ ├── form-commands.js (Stores form-related functions, based on the framework, consistent with the operation of form items)
|
||||
│ │ ├── index.js
|
||||
│ │ ├── resource-commands.js (Storage functions related to resource operations, such as creating cloud hosts, creating routes, deleting resources, etc.)
|
||||
│ │ └── table-commands.js (Storage the functions related to the resource list, based on the framework, have consistency in the operation of the list)
|
||||
│ │ ├── resource-commands.js (Store functions related to resource operations, such as creating instance, creating router, deleting resources, etc.)
|
||||
│ │ └── table-commands.js (Store the functions related to the resource list based on the framework, and it has consistency in the operation of the lis)
|
||||
│ └── utils (Store the read function for the configuration file)
|
||||
│ └── index.js
|
||||
└── unit (Unit test)
|
||||
├── local-storage-mock.js ( Storeage mock function in local)
|
||||
├── local-storage-mock.js ( Storage mock function in local)
|
||||
├── locales (Translation files used when testing internationalization)
|
||||
│ ├── en-US.js
|
||||
│ └── zh-CN.js
|
||||
@ -82,10 +82,10 @@ test
|
||||
└── svg-mock.js (Mock of image loading)
|
||||
```
|
||||
|
||||
- E2E test code, storaged in the `test/e2e` directory
|
||||
- Other global configurations of E2E storaged in `cypress.json`
|
||||
- The basic code of the unit test storaged in the `test/unit` directory
|
||||
- Other global configuration of unit test, storaged in `jest.config.js`
|
||||
- E2E test code, stored in the `test/e2e` directory
|
||||
- Other global configurations of E2E are stored in `cypress.json`
|
||||
- The basic code of the unit test is stored in the `test/unit` directory
|
||||
- Other global configuration of unit test, stored in `jest.config.js`
|
||||
- The test code of the unit test is usually placed in the same directory as the file to be tested, and has a suffix of `test.js` or `spec.js`
|
||||
- case：`src/utils/index.js`与`src/utils/index.test.js`
|
||||
- case：`src/utils/local-storage.js`与`src/utils/local-storage.spec.js`
|
||||
- case：`src/utils/index.js` and `src/utils/index.test.js`
|
||||
- case：`src/utils/local-storage.js` and `src/utils/local-storage.spec.js`
|
||||
|
||||
@ -4,14 +4,14 @@ For specific introduction and usage of Cypress, please refer to[Official documen
|
||||
|
||||
Here we mainly give the E2E use cases corresponding to the resources in the front-end page of Skyline-console, and use function defined in `test/e2e/support`
|
||||
|
||||
The following is an introduction, taking the cloud host use case `test/e2e/integration/pages/compute/instance.spec.js` as an example
|
||||
The following is an introduction, taking the instance use case `test/e2e/integration/pages/compute/instance.spec.js` as an example
|
||||
|
||||
Generally, when testing the corresponding functions of a resource, follow the following order
|
||||
|
||||
1. Prepare relevant variables in text
|
||||
- Required parameters when creating a resource, such as: name, password
|
||||
- Required parameters when editing resources, such as: new name
|
||||
- When creating an associated resource, the name of the associated resource, such as: network name, router name, cloud disk name
|
||||
- When creating an associated resource, the name of the associated resource, such as: network name, router name, volume name
|
||||
|
||||
```javascript
|
||||
const uuid = Cypress._.random(0, 1e6);
|
||||
@ -24,8 +24,8 @@ Generally, when testing the corresponding functions of a resource, follow the fo
|
||||
```
|
||||
|
||||
2. Login before operation
|
||||
- If is operate console resource, use`cy.login`
|
||||
- If is operate administrator resource, use`cy.loginAdmin`
|
||||
- If you are operating console resources, please use `cy.login`
|
||||
- If you are operating administrator resource, please use`cy.loginAdmin`
|
||||
- Generally, the variable `listUrl` is used in the `login` and `loginAdmin` functions, that is, directly access the page where the resource is located after logging in
|
||||
|
||||
```javascript
|
||||
@ -41,7 +41,7 @@ Generally, when testing the corresponding functions of a resource, follow the fo
|
||||
cy.createNetwork({ name: networkName });
|
||||
```
|
||||
|
||||
- Create router`cy.createRouter`，Used to ensure that the floating IP is reachable when testing the associated floating IP
|
||||
- Create router`cy.createRouter`to ensure that the floating IP is reachable when testing the associated floating IP
|
||||
- The router created in the following way will open the external network gateway and bind the subnet of the `networkName` network
|
||||
|
||||
```javascript
|
||||
@ -63,7 +63,7 @@ Generally, when testing the corresponding functions of a resource, follow the fo
|
||||
4. Write cases for creating resources
|
||||
5. Write use cases for accessing resource details
|
||||
6. Write use cases corresponding to all operations of resources separately
|
||||
- Generally, the use case of the `edit` operation is written at the back, and then the use case of the `delete` operation is written, so that you can test whether the editing is effective
|
||||
- Generally, the use case of the `edit` operation is written later, and then the use case of the `delete` operation is written, so that you can test whether the editing is effective
|
||||
7. To delete associated resources, use the resource-deleting function provided in `resource-commands.js`, this is to make the resources in the test account as clean as possible after the test case is executed
|
||||
- Delete Floating IP
|
||||
|
||||
@ -97,8 +97,8 @@ Generally, when testing the corresponding functions of a resource, follow the fo
|
||||
|
||||
The `4`, `5`, and `6` in the above steps are mainly used
|
||||
|
||||
- The function operation form in `test/e2e/support/form-commands.js`, please refer to the detailed introduction[3-1-E2E-表单操作](3-1-E2E-表单操作.md)
|
||||
- The functions in `test/e2e/support/table-commands.js`, click on the buttons in the operation table, search, and enter for details. please refer to the detailed introduction[3-2-E2E-表格操作](3-2-E2E-表格操作.md)
|
||||
- The functions in `test/e2e/support/detail-commands.js`, the operation returns the list page, the detection details, and the switching details Tab. please refer to the detailed introduction[3-3-E2E-详情操作](3-3-E2E-详情操作.md)
|
||||
- The function operation form in `test/e2e/support/form-commands.js`, please refer to the detailed introduction[3-1-E2E-form-operation](3-1-E2E-form-operation.md)
|
||||
- The functions in `test/e2e/support/table-commands.js`, click on the buttons in the operation table, search, and enter for details. please refer to the detailed introduction[3-2-E2E-table-operation](3-2-E2E-table-operation.md)
|
||||
- The functions in `test/e2e/support/detail-commands.js`, the operation returns the list page, the detection details, and the switching details Tab. please refer to the detailed introduction[3-3-E2E-detail-operation](3-3-E2E-detail-operation.md)
|
||||
|
||||
Create and delete associated resources mainly use the functions in `test/e2e/support/resource-commands.js`,. please refer to the detailed introduction[3-4-E2E-资源操作](3-4-E2E-资源操作.md)
|
||||
Create and delete associated resources mainly use the functions in `test/e2e/support/resource-commands.js`,. please refer to the detailed introduction[33-4-E2E-resource-operation](3-4-E2E-resource-operation.md)
|
||||
@ -37,8 +37,8 @@ Because of the consistency of the front-end framework, when we write related use
|
||||
|
||||
|
||||
- `checkDisableAction`
|
||||
- When some data does not meet the requirements, use the batch operation, an error will pop up. This function verifies that the data does not meet the operation requirements, and closes the error prompt
|
||||
- Take the locked instance `test/e2e/integration/pages/compute/instance.spec.js` as an example
|
||||
- If some data does not meet the requirements, an error will pop up when using batch operations. This function verifies that the data does not meet the operation requirements, and closes the error prompt
|
||||
- Take the locked instance as an example: `test/e2e/integration/pages/compute/instance.spec.js`
|
||||
- After locking, it no longer supports startup, shutdown, and restart operations
|
||||
|
||||
```javascript
|
||||
@ -61,7 +61,7 @@ Because of the consistency of the front-end framework, when we write related use
|
||||
|
||||
- `clickStepActionNextButton`
|
||||
- Click the Next/Confirm button of the step-by-step form
|
||||
- Take the create instance use case `test/e2e/integration/pages/compute/instance.spec.js` as an example
|
||||
- Take the create instance use case as an example: `test/e2e/integration/pages/compute/instance.spec.js`
|
||||
- A total of 3 clicks on the next step and 1 confirmation button
|
||||
|
||||
```javascript
|
||||
@ -206,7 +206,7 @@ Looking at the structure and style of the elements through the page, I found tha
|
||||
- `formTableNotSelectAll`
|
||||
- Click Select all checkbox of the selection type form cancel select all item
|
||||
- Parameter `formItemName`, which is the `name` value of `formItem` in the development code
|
||||
- Take the Host Aggregates management instance without selecting the instance `test/e2e/integration/pages/compute/aggregate.spec.js` as an example
|
||||
- Take the Host Aggregates management instance without selecting the instance as an example: `test/e2e/integration/pages/compute/aggregate.spec.js`
|
||||
|
||||
```javascript
|
||||
it('successfully manage host: no host', () => {
|
||||
@ -315,7 +315,7 @@ Looking at the structure and style of the elements through the page, I found tha
|
||||
|
||||
|
||||
|
||||
- Take the network QoS policy to create the bandwidth limit rule and set the direction to "inbound" `test/e2e/integration/pages/network/qos-policy.spec.js` as an example
|
||||
- Take the network QoS policy to create the bandwidth limit rule and set the direction to "inbound" as an example: `test/e2e/integration/pages/network/qos-policy.spec.js`
|
||||
|
||||
```javascript
|
||||
it('successfully create bandwidth ingress limit rule', () => {
|
||||
@ -352,7 +352,7 @@ Looking at the structure and style of the elements through the page, I found tha
|
||||
- Operations on form items of AttachFile type
|
||||
- Parameter `formItemName`, which is the `name` value of `formItem` in the development code
|
||||
- The parameter `filename`, the name of the uploaded file, the file needs to be saved in the `test/e2e/fixtures` directory in advance
|
||||
- Take the creation of a key selection file as an example `test/e2e/integration/pages/compute/keypair.spec.js` as an example
|
||||
- Take the creation of a key selection file as an example as an example: `test/e2e/integration/pages/compute/keypair.spec.js`
|
||||
|
||||
```javascript
|
||||
it('successfully create by file', () => {
|
||||
@ -397,7 +397,7 @@ Looking at the structure and style of the elements through the page, I found tha
|
||||
- `formAddSelectAdd`
|
||||
- Operations on form item of AddSelect type
|
||||
- Parameter `formItemName`, which is the `name` value of `formItem` in the development code
|
||||
- Take the Host Aggregates management metedata add custom metadata`test/e2e/integration/pages/compute/aggregate.spec.js`as an example
|
||||
- Take the Host Aggregates management metedata add custom metadata as an example: `test/e2e/integration/pages/compute/aggregate.spec.js`
|
||||
|
||||
```javascript
|
||||
it('successfully manage metadata', () => {
|
||||
@ -478,7 +478,7 @@ Looking at the structure and style of the elements through the page, I found tha
|
||||
- Specify the items to be selected based on the search display in the transfer on the right对右侧的穿梭框基于搜索展示指定待选条目
|
||||
- Parameter `formItemName`, which is the `name` value of `formItem` in the development code
|
||||
- Parameter `value`, search content
|
||||
- Take the user group management user `test/e2e/integration/pages/identity/user-group.spec.js` as an example
|
||||
- Take the user group management user as an example: `test/e2e/integration/pages/identity/user-group.spec.js`
|
||||
|
||||
```javascript
|
||||
it('successfully manage user', () => {
|
||||
@ -521,7 +521,7 @@ Looking at the structure and style of the elements through the page, I found tha
|
||||
- Parameter `formItemName`, which is the `name` value of `formItem` in the development code
|
||||
- Parameter `key`, the content of input on the left
|
||||
- Parameter `value`, the content of input on the right
|
||||
- Take the Host Aggregates management metedata add custom metadata`test/e2e/integration/pages/compute/aggregate.spec.js`as an example
|
||||
- Take the Host Aggregates management metedata add custom metadata as an example: `test/e2e/integration/pages/compute/aggregate.spec.js`
|
||||
|
||||
```javascript
|
||||
it('successfully manage metadata', () => {
|
||||
@ -543,7 +543,7 @@ Looking at the structure and style of the elements through the page, I found tha
|
||||
2. Click the direction button in the middle of the transfer to make the selected content enter the transfer on the right
|
||||
- Parameter `formItemName`, which is the `name` value of `formItem` in the development code
|
||||
- Parameter `index`, the index of the node
|
||||
- Take the Host Aggregates management metedata add custom metadata`test/e2e/integration/pages/compute/aggregate.spec.js`as an example
|
||||
- Take the Host Aggregates management metedata add custom metadata as an example: `test/e2e/integration/pages/compute/aggregate.spec.js`
|
||||
|
||||
```javascript
|
||||
it('successfully manage metadata', () => {
|
||||
|
||||
@ -107,7 +107,7 @@ Mainly include: waiting for the list to load
|
||||
- Parameter `name`, the name of the search term
|
||||
- Parameter `value`, the content of the input
|
||||
- By searching, the resource to be operated is located in the first row of the table for subsequent operations
|
||||
- Take the creation of the stack `test/e2e/integration/pages/heat/stack.spec.js` as an example
|
||||
- Take the creation of the stack as an example: `test/e2e/integration/pages/heat/stack.spec.js`
|
||||
1. After creation, enter the resource list page
|
||||
2. Search by name on the list page
|
||||
3. Wait for the status of the resource to be available
|
||||
@ -161,7 +161,7 @@ Mainly include: waiting for the list to load
|
||||
- Visit the detail page of the first row of resources and wait for the detail page to load
|
||||
- Parameter `index`, the subscript of the column where the link is located, the default is `1`
|
||||
- Parameter `waitTime`, the time to wait after loading the details page
|
||||
- Take the image `test/e2e/integration/pages/compute/image.spec.js` as an example
|
||||
- Take the image as an example: `test/e2e/integration/pages/compute/image.spec.js`
|
||||
1. Search
|
||||
2. Enter the details page
|
||||
3. Verification details name
|
||||
@ -183,7 +183,7 @@ Mainly include: waiting for the list to load
|
||||
- Verify that the content of the specified column in the first row meets expectations
|
||||
- Parameter `columnIndex`, which specifies the index of the column
|
||||
- Parameter `value`, the expected value
|
||||
- Take the instance `test/e2e/integration/pages/compute/image.spec.js` as an example
|
||||
- Take the instance as an example: `test/e2e/integration/pages/compute/image.spec.js`
|
||||
1. Search
|
||||
2. Stop the instance
|
||||
3. Verify that the status of the instance is `Stop`
|
||||
@ -236,7 +236,7 @@ Mainly include: waiting for the list to load
|
||||
- `waitStatusActiveByRefresh`
|
||||
- Click the refresh button above the table every 5 seconds until the resource status becomes available
|
||||
- After a resource is created or changed, it often takes a certain amount of time to become available before subsequent operations can be performed
|
||||
- Take the creation of the stack `test/e2e/integration/pages/heat/stack.spec.js` as an example
|
||||
- Take the creation of the stack as an example: `test/e2e/integration/pages/heat/stack.spec.js`
|
||||
|
||||
```javascript
|
||||
it('successfully create', () => {
|
||||
@ -275,7 +275,7 @@ The buttons above the table generally include: refresh, create, batch operation
|
||||
- Parameter `buttonIndex`, the subscript of the button above the table
|
||||
- Parameter `waitTime`, the waiting time after clicking, the default is 2 seconds
|
||||
- Generally, the subscript of the created button is 1
|
||||
- Take the creat key pair `test/e2e/integration/pages/compute/keypair.spec.js` as an example
|
||||
- Take the creat key pair as an example: `test/e2e/integration/pages/compute/keypair.spec.js`
|
||||
|
||||
```javascript
|
||||
it('successfully create', () => {
|
||||
@ -292,7 +292,7 @@ The buttons above the table generally include: refresh, create, batch operation
|
||||
- Click the button above the table by name, generally used for batch operation button clicks
|
||||
- Parameter `title`, the text on the button above the table
|
||||
- Parameter `waitTime`, the waiting time after clicking, the default is 2 seconds
|
||||
- Take the shut off operation of the instance in the close state `test/e2e/integration/pages/compute/instance.spec.js` as an example
|
||||
- Take the shut off operation of the instance in the close state as an example: `test/e2e/integration/pages/compute/instance.spec.js`
|
||||
- Click the close button at the top of the form
|
||||
|
||||
```javascript
|
||||
@ -316,7 +316,7 @@ The buttons above the table generally include: refresh, create, batch operation
|
||||
2. Click the `Confirm` button
|
||||
- Parameter `title`, the text on the button above the table
|
||||
- Parameter `waitTime`, the waiting time after clicking, the default is 2 seconds
|
||||
- Take the release of floating IP `test/e2e/integration/pages/network/floatingip.spec.js` as an example
|
||||
- Take the release of floating IP as an example: `test/e2e/integration/pages/network/floatingip.spec.js`
|
||||
- Select all floating IPs in the stopped state and release them in batches
|
||||
|
||||
```javascript
|
||||
@ -376,7 +376,7 @@ The buttons above the table generally include: refresh, create, batch operation
|
||||
|
||||
- `clickActionInMore`
|
||||
- Click the operation in `More` in the first row according to the title
|
||||
- Take the create instance button `test/e2e/integration/pages/compute/image.spec.js` as an example
|
||||
- Take the create instance button as an example: `test/e2e/integration/pages/compute/image.spec.js`
|
||||
|
||||
```javascript
|
||||
it('successfully create instance with cancel', () => {
|
||||
@ -414,7 +414,7 @@ The buttons above the table generally include: refresh, create, batch operation
|
||||
- Parameter `title`, the name of the operation
|
||||
- Parameter `name`, the name of the resource
|
||||
- After the resource is in certain states, some operations need to be disabled, the first operation in the row operation list, if it is not operable, it is in the `disabled` state, and the operations in `more`, if not available , Don’t show
|
||||
- Take the router `test/e2e/integration/pages/network/router.spec.js` as an example
|
||||
- Take the router as an example: `test/e2e/integration/pages/network/router.spec.js`
|
||||
1. Open the public network gateway when creating the router
|
||||
2. Verify that the router cannot be deleted, that is, there is no `Delete` button
|
||||
|
||||
|
||||
@ -5,7 +5,7 @@ Because of the consistency of the front-end framework, we often find that there
|
||||
- `checkDetailName`
|
||||
- Verify that the header of the detail page contains the specified resource name
|
||||
- Parameter `name`, resource name
|
||||
- Take viewing key detail `test/e2e/integration/pages/compute/keypair.spec.js` as an example
|
||||
- Take viewing key detail as an example: `test/e2e/integration/pages/compute/keypair.spec.js`
|
||||
|
||||
```javascript
|
||||
it('successfully detail', () => {
|
||||
@ -23,7 +23,7 @@ Because of the consistency of the front-end framework, we often find that there
|
||||
- Click the `Back` button on the detail page to enter the list page and wait for the list to load
|
||||
- Parameter `url`, list url
|
||||
- If set, it will verify whether the returned list route meets expectations
|
||||
- Take viewing key detail `test/e2e/integration/pages/compute/keypair.spec.js` as an example
|
||||
- Take viewing key detail as an example: `test/e2e/integration/pages/compute/keypair.spec.js`
|
||||
1. Search
|
||||
2. Verify that the first row of the form contains the specified name
|
||||
3. Enter the detail page
|
||||
@ -46,7 +46,7 @@ Because of the consistency of the front-end framework, we often find that there
|
||||
- Click the `Back` button on the detail page to enter the list page and wait for the list to load
|
||||
- Parameter `url`, list url
|
||||
- If set, it will verify whether the returned list route meets expectations
|
||||
- Take viewing key detail `test/e2e/integration/pages/compute/keypair.spec.js` as an example
|
||||
- Take viewing key detail as an example: `test/e2e/integration/pages/compute/keypair.spec.js`
|
||||
1. Search
|
||||
2. Verify that the first row of the form contains the specified name
|
||||
3. Enter the detail page
|
||||
@ -71,7 +71,7 @@ Because of the consistency of the front-end framework, we often find that there
|
||||
- Parameter `urlTab`, the tab attribute in the route
|
||||
- If set, it will verify whether the tab attribute in the route is as expected after switching the label
|
||||
- Parameter `waitTime`, the waiting time after switching labels
|
||||
- Take viewing network details `test/e2e/integration/pages/network/network.spec.js` as an example
|
||||
- Take viewing network details as an example: `test/e2e/integration/pages/network/network.spec.js`
|
||||
1. Search
|
||||
2. Verify that the first row of the form contains the specified name
|
||||
3. Enter the details page
|
||||
|
||||
@ -6,7 +6,7 @@ In the E2E process, when creating a resource, it is often necessary to create th
|
||||
- Create instance and wait for the instance to become `running`
|
||||
- Parameter `name`, the name of the instance
|
||||
- Parameter `networkName`, the network name selected when the instance was created
|
||||
- Take the floating IP associated instance `test/e2e/integration/pages/network/floatingip.spec.js` as an example
|
||||
- Take the floating IP associated instance as an example: `test/e2e/integration/pages/network/floatingip.spec.js`
|
||||
- In order to successfully associate with the instance, the router connected to the subnet where the instance's interfae is located must have a public network gateway turned on
|
||||
1. Create a network `networkName` with subnet
|
||||
2. Create a router `routerName` with the public network gateway turned on and connected to the network `networkName` subnet
|
||||
@ -24,7 +24,7 @@ In the E2E process, when creating a resource, it is often necessary to create th
|
||||
- Create a network with a subnet
|
||||
- Parameter `name`, the name of the network
|
||||
- Parameter `networkName`, the network name selected when the instance was created
|
||||
- Take the router connected to the subnet as an example `test/e2e/integration/pages/network/router.spec.js` as an example
|
||||
- Take the router connected to the subnet as an example: `test/e2e/integration/pages/network/router.spec.js`
|
||||
- Created a network named `networkName` in preparation for connecting to subnets
|
||||
|
||||
```javascript
|
||||
@ -36,7 +36,7 @@ In the E2E process, when creating a resource, it is often necessary to create th
|
||||
- `createNetworkPolicy`
|
||||
- Create network QoS policy
|
||||
- Parameter `name`, the name of the strategy
|
||||
- Take virtual adapter modification QoS as an example `test/e2e/integration/pages/network/virtual-adapter.spec.js` as an example
|
||||
- Take virtual adapter modification QoS as an example: `test/e2e/integration/pages/network/virtual-adapter.spec.js`
|
||||
- Created a policy named `policyName` in preparation for modifying QoS
|
||||
|
||||
```javascript
|
||||
@ -50,7 +50,7 @@ In the E2E process, when creating a resource, it is often necessary to create th
|
||||
- Parameter `name`, the name of the router
|
||||
- Parameter `network`
|
||||
- If set, the router will connect to the subnet of the `network` network
|
||||
- Take the floating IP associated instance `test/e2e/integration/pages/network/floatingip.spec.js` as an example
|
||||
- Take the floating IP associated instance as an example: `test/e2e/integration/pages/network/floatingip.spec.js`
|
||||
- In order to successfully associate with the instance, the router connected to the subnet where the instance's interfae is located must have a public network gateway turned on
|
||||
1. Create a network `networkName` with subnets
|
||||
2. Create a router `routerName` with the public network gateway turned on and connected to the network `networkName` subnet
|
||||
@ -70,7 +70,7 @@ In the E2E process, when creating a resource, it is often necessary to create th
|
||||
- If set, you need to disconnect the router's subnet first
|
||||
- Parameter `name`, the name of the router
|
||||
|
||||
- Take the floating IP to delete the associated resource `test/e2e/integration/pages/network/floatingip.spec.js` as an example
|
||||
- Take the floating IP to delete the associated resource as an example: `test/e2e/integration/pages/network/floatingip.spec.js`
|
||||
- In order to successfully associate with the instance, the router connected to the subnet where the instance's interfae is located must have a public network gateway turned on
|
||||
|
||||
```javascript
|
||||
@ -86,7 +86,7 @@ In the E2E process, when creating a resource, it is often necessary to create th
|
||||
- `forceDeleteInstance`
|
||||
- Force delete instance instead of soft delete
|
||||
- Parameter `name`, the name of the instance
|
||||
- Take deleting the instance group `test/e2e/integration/pages/compute/server-group.spec.js` as an example
|
||||
- Take deleting the instance group as an example: `test/e2e/integration/pages/compute/server-group.spec.js`
|
||||
1. Delete the instance under the instance group first
|
||||
2. Then successfully delete the instance group
|
||||
|
||||
@ -105,7 +105,7 @@ In the E2E process, when creating a resource, it is often necessary to create th
|
||||
- `createVolume`
|
||||
- Create volume
|
||||
- Parameter `name`, the name of the volume
|
||||
- Take volume backup `test/e2e/integration/pages/storage/backup.spec.js` as an example
|
||||
- Take volume backup as an example: `test/e2e/integration/pages/storage/backup.spec.js`
|
||||
- To create a volume backup, you need to prepare the volume first
|
||||
|
||||
```javascript
|
||||
@ -119,7 +119,7 @@ In the E2E process, when creating a resource, it is often necessary to create th
|
||||
- `createSecurityGrouop`
|
||||
- Create a security group
|
||||
- Parameter `name`, the name of the security group
|
||||
- Take the virtual adapter card `test/e2e/integration/pages/network/virtual-adapter.spec.js` as an example
|
||||
- Take the virtual adapter card as an example: `test/e2e/integration/pages/network/virtual-adapter.spec.js`
|
||||
-To test management security group, you need to prepare the security group first
|
||||
|
||||
```javascript
|
||||
@ -134,7 +134,7 @@ In the E2E process, when creating a resource, it is often necessary to create th
|
||||
|
||||
- `createFip`
|
||||
- Create floating ip
|
||||
- Take instance `test/e2e/integration/pages/compute/instance.spec.js`as an example
|
||||
- Take instance as an example: `test/e2e/integration/pages/compute/instance.spec.js`
|
||||
- Test associate floating IP, you need to prepare reachable floating IP
|
||||
|
||||
```javascript
|
||||
@ -149,7 +149,7 @@ In the E2E process, when creating a resource, it is often necessary to create th
|
||||
- `createUserGroup`
|
||||
- Create user group
|
||||
- Parameter `name`, the name of user group
|
||||
- Take project `test/e2e/integration/pages/identity/project.spec.js`as an example
|
||||
- Take project as an example: `test/e2e/integration/pages/identity/project.spec.js`
|
||||
- To test management user group, you need to prepare the user group
|
||||
|
||||
```javascript
|
||||
@ -162,7 +162,7 @@ In the E2E process, when creating a resource, it is often necessary to create th
|
||||
- `createUser`
|
||||
- Create user
|
||||
- Parameter `name`, user name
|
||||
- Take project `test/e2e/integration/pages/identity/project.spec.js`as an example
|
||||
- Take project as an example: `test/e2e/integration/pages/identity/project.spec.js`
|
||||
- To test management user, you need to prepare user
|
||||
|
||||
```javascript
|
||||
@ -175,7 +175,7 @@ In the E2E process, when creating a resource, it is often necessary to create th
|
||||
- `createProject`
|
||||
- Create project
|
||||
- Parameter`name`, the name of project
|
||||
- Take user`test/e2e/integration/pages/identity/user.spec.js`as an example
|
||||
- Take user as an example: `test/e2e/integration/pages/identity/user.spec.js`
|
||||
- To test creater user, need to prepare project
|
||||
- To test management project permission， need to prepare project
|
||||
|
||||
@ -190,7 +190,7 @@ In the E2E process, when creating a resource, it is often necessary to create th
|
||||
- `createIronicImage`
|
||||
- Create image for ironic
|
||||
- Parameter `name`, the name of the image
|
||||
- Take ironic `test/e2e/integration/pages/compute/ironic.spec.js` as an example
|
||||
- Take ironic as an example: `test/e2e/integration/pages/compute/ironic.spec.js`
|
||||
- Create a ironic, image need to be able to create a ironic
|
||||
|
||||
```javascript
|
||||
@ -206,7 +206,7 @@ In the E2E process, when creating a resource, it is often necessary to create th
|
||||
- Delete instance
|
||||
- Parameter `name`, name of instance
|
||||
- Parameter `deleteRecycleBin`, Default `true`, Indicates that you need to enter the recycle bin to delete again
|
||||
- Take delete instance `test/e2e/integration/pages/compute/instance.spec.js` as an example
|
||||
- Take delete instance as an example: `test/e2e/integration/pages/compute/instance.spec.js`
|
||||
|
||||
```javascript
|
||||
it('successfully delete', () => {
|
||||
@ -216,7 +216,7 @@ In the E2E process, when creating a resource, it is often necessary to create th
|
||||
|
||||
- `deleteAllAvailableVolume`
|
||||
-Delete all availablevolume
|
||||
-Take instance `test/e2e/integration/pages/compute/instance.spec.js` as an example
|
||||
-Take instance as an example: `test/e2e/integration/pages/compute/instance.spec.js`
|
||||
|
||||
```javascript
|
||||
it('successfully delete related resources', () => {
|
||||
@ -266,7 +266,7 @@ In the E2E process, when creating a resource, it is often necessary to create th
|
||||
- If not set, all resources under the resource list will be deleted
|
||||
- Parameter `tab`
|
||||
- If set, it means that the resource is located under the tab `tab`, you need to switch to the specified tab first
|
||||
- Take the volume type `test/e2e/integration/pages/storage/volume-type.spec.js` as an example
|
||||
- Take the volume type as an example: `test/e2e/integration/pages/storage/volume-type.spec.js`
|
||||
- Delete the QoS prepared when managing QoS
|
||||
|
||||
```javascript
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user