|
1 | | -# Table of contents |
2 | | -> ITE Intro \ |
| 1 | +# Table of contents |
3 | 2 | > Editor components \ |
4 | | -> GUI Testing components \ |
5 | | -> WEB Testing components \ |
6 | | -> API Testing components \ |
7 | | -> Load & Stress Testing components |
| 3 | +> GUI components \ |
| 4 | +> WEB components \ |
| 5 | +> API components \ |
| 6 | +> Load components |
8 | 7 | --- |
9 | | -## What is ITE |
| 8 | +## What is Automation Editor |
10 | 9 | > Project Kanban \ |
11 | | -> https://github.com/orgs/Integrated-Testing-Environment/projects/4/views/1 \ |
12 | | -> Integrated Testing Environment (ITE) |
13 | | -> * ITE mainly provides an integrated automated testing environment. |
14 | | -> * ITE is composed of the following components: |
| 10 | +> https://github.com/orgs/Intergration-Automation-Testing/projects/2/views/1 \ |
| 11 | +> Tool for automation |
| 12 | +> * Automation Editor is composed of the following components: |
15 | 13 | >> * Editor。 |
16 | | ->> * GUI Testing。 |
17 | | ->> * Web Testing。 |
18 | | ->> * API Testing。 |
19 | | ->> * Load & Stress Testing。 |
20 | | ---- |
21 | | -## ITE Testing |
22 | | - |
23 | | -> How does ITE perform self-testing? |
24 | | -> * CircleCI & GitHub Actions。 |
25 | | ->> * What are the benefits of using CircleCI and GitHub Actions? |
26 | | ->> * They provide GitHub/Gitlab hooks for automated testing on every commit. |
27 | | ->> * They provide detailed test logs. |
28 | | ->> * They allow for automatic deployment to selected environments. |
29 | | ->> * They make it easy to specify branches for testing. |
30 | | ->> * They can parallelize multiple tests for faster execution. |
31 | | ---- |
32 | | -## ITE Dev |
33 | | -> * ITE's development process: CI/CD (Continuous Integration/Continuous Deployment). |
34 | | -> * Continuous Integration: The longer the code is away from the last update, the higher the risk, so continuous integration encourages committing and automated testing after completing each part to reduce risk. |
35 | | -> * Continuous Deployment: Continuously deploying the code to the real environment for testing, usually achieved through automation. |
| 14 | +>> * GUI Automation。 |
| 15 | +>> * Web Automation。 |
| 16 | +>> * API Automation。 |
| 17 | +>> * Load Automation。 |
36 | 18 | --- |
37 | 19 | ### JEditor |
38 | 20 | > * JEditor is a simple text editor, but it has all the necessary features. |
|
49 | 31 | >> * Run shell commands. |
50 | 32 | --- |
51 | 33 | ### GUI Testing components |
52 | | -> Image & Coordinate based GUI Testing \ |
53 | | -> GUI automated testing based on image comparison and coordinates. \ |
| 34 | +> Image & Coordinate based GUI Automation \ |
| 35 | +> GUI automated based on image comparison and coordinates. \ |
54 | 36 | > Cross-platform and cross-programming language.\ |
55 | 37 | > Solve problems: |
56 | 38 | >> * Provide automation execution for repetitive tasks. |
|
62 | 44 | >> * Can use keywords for development to improve readability. |
63 | 45 | --- |
64 | 46 | ### WEB Testing components |
65 | | -> Multiton Selenium Instance testing \ |
66 | | -> The WEB Testing component is a web automation testing solution based on Selenium. \ |
| 47 | +> Multiton Selenium Instance Automation \ |
| 48 | +> The WEB Automation component is a web automation solution based on Selenium. \ |
67 | 49 | > It wraps Selenium and therefore has all the functionality of Selenium. \ |
68 | 50 | > What problems does it solve? |
69 | 51 | >> * Automatically downloads and updates the required web driver, so users no longer need to install it manually. |
|
74 | 56 | >> * Offers a CLI mode for Web Testing. |
75 | 57 | --- |
76 | 58 | ### API Testing components |
77 | | -> Simple way to testing HTTP/S & Soap \ |
| 59 | +> Simple way to Automation Requests HTTP/S & Soap \ |
78 | 60 | > Wrapper for Requests package, designed for those with experience using Requests. \ |
79 | 61 | > Send HTTP/S and SOAP requests with a simple line of code or keyword. \ |
80 | 62 | > Detailed information on Requests and Responses. \ |
|
96 | 78 |
|
97 | 79 | ### Features |
98 | 80 |
|
99 | | -> * ITE GUI for beginner |
100 | | -> * GUI testing (use AutoControl) |
101 | | -> * API testing (use APITestka) |
102 | | -> * Web testing (use WebRunner) |
103 | | -> * Loading testing (use LoadDensity) |
104 | | -> * Multi test task runner (multi process) |
| 81 | +> * GUI Automation (use AutoControl) |
| 82 | +> * API Automation (use APITestka) |
| 83 | +> * Web Automation (use WebRunner) |
| 84 | +> * Loading Automation (use LoadDensity) |
| 85 | +> * Multi test task runner (multiprocess, but without AutoControl) |
105 | 86 | > * you can run multi testing on same time |
106 | 87 | > * open log window to check testing result |
107 | 88 | > * Send mail when testing failure (need to setting mail) |
|
112 | 93 |
|
113 | 94 | [](https://dl.circleci.com/status-badge/redirect/gh/Integrated-Testing-Environment/Integration-testing-environment/tree/main) |
114 | 95 |
|
115 | | -[](https://github.com/JE-Chen/Integration-testing-environment/actions/workflows/ITE-github-actions_dev.yml) |
| 96 | +[](https://github.com/JE-Chen/Integration-testing-environment/actions/workflows/ITE-github-actions_dev.yml) |
116 | 97 |
|
117 | | -[](https://github.com/JE-Chen/Integration-testing-environment/actions/workflows/ITE-github-actions_stable.yml) |
| 98 | +[](https://github.com/JE-Chen/Integration-testing-environment/actions/workflows/ITE-github-actions_stable.yml) |
118 | 99 |
|
119 | 100 | ### install |
120 | 101 | #### we suggest install full package |
121 | | -* pip install integration_testing_environment[full_extension] |
| 102 | +* pip install automation_editor[full_extension] |
122 | 103 | #### if we don't want to use send after test |
123 | | -* pip install integration_testing_environment |
| 104 | +* pip install automation_editor |
0 commit comments