Skip to content

Commit a7ca574

Browse files
JE-ChenJE-Chen
committed
edit readme.md
edit readme.md
1 parent 3f8c099 commit a7ca574

File tree

4 files changed

+100
-20
lines changed

4 files changed

+100
-20
lines changed

‎.gitignore‎

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,5 @@
1+
# IDEA
2+
.idea/
13
# Byte-compiled / optimized / DLL files
24
__pycache__/
35
*.py[cod]

‎README.md‎

Lines changed: 94 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -1,24 +1,102 @@
1-
# Integration-testing-environment as Integration Test Environment(ITE)
2-
1+
# Table of contents
2+
> ITE Intro \
3+
> Editor components \
4+
> GUI Testing components \
5+
> WEB Testing components \
6+
> API Testing components \
7+
> Load & Stress Testing components
38
---
4-
5-
## Now ITE support: GUI, API, Web, Loading. Testing
6-
7-
### Maybe will add app testing maybe
8-
9+
## What is ITE
10+
11+
> Integrated Testing Environment (ITE)
12+
> * ITE mainly provides an integrated automated testing environment.
13+
> * ITE is composed of the following components:
14+
>> * Editor。
15+
>> * GUI Testing。
16+
>> * Web Testing。
17+
>> * API Testing。
18+
>> * Load & Stress Testing。
19+
---
20+
## ITE Testing
21+
22+
> How does ITE perform self-testing?
23+
> * CircleCI & Github Actions。
24+
>> * What are the benefits of using CircleCI and Github Actions?
25+
>> * They provide Github/Gitlab hooks for automated testing on every commit.
26+
>> * They provide detailed test logs.
27+
>> * They allow for automatic deployment to selected environments.
28+
>> * They make it easy to specify branches for testing.
29+
>> * They can parallelize multiple tests for faster execution.
30+
---
31+
## ITE Dev
32+
> * ITE's development process: CI/CD (Continuous Integration/Continuous Deployment).
33+
> * 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.
34+
> * Continuous Deployment: Continuously deploying the code to the real environment for testing, usually achieved through automation.
35+
---
36+
### Editor components
37+
> A simple text editor for ite
38+
>> Editor Really?
39+
>> * Why do we need to provide an editor when there are so many text editors and IDEs available?
40+
>> * We provide an editor as a cross-platform and minimalistic solution that comes with ITE, without requiring additional installation. The editor provides basic functionality, including font adjustment, support for other ITE components, basic file management such as saving, opening, and auto-saving, as well as file encoding and code selection integration. Additionally, the editor allows users to view test results through the interface.
41+
>> * The term "minimalistic" refers to the basic functionalities that are essential for a text editor, without the advanced features commonly found in other IDEs or text editors.
42+
---
43+
### GUI Testing components
44+
> Image & Coordinate based GUI Testing \
45+
> GUI automated testing based on image comparison and coordinates. \
46+
> Cross-platform and cross-programming language.\
47+
> Solve problems:
48+
>> * Provide automation execution for repetitive tasks.
49+
>> * Multiple methods are available, including recording, image recognition, and coordinate-based testing.
50+
>> * Tests can be executed remotely through TCP/IP.
51+
>> * Test reports can be generated with records for each action.
52+
>> * The same code can be used for three platforms, reducing the possibility of platform-dependent programs.
53+
>> * Provide hooks for keyboard and mouse events and state checks (including using code to simulate key presses).
54+
>> * Can use keywords for development to improve readability.
55+
---
56+
### WEB Testing components
57+
> Multiton Selenium Instance testing \
58+
> The WEB Testing component is a web automation testing solution based on Selenium. \
59+
> It wraps Selenium and therefore has all the functionality of Selenium. \
60+
> What problems does it solve?
61+
>> * Automatically downloads and updates the required web driver, so users no longer need to install it manually.
62+
>> * Provides the ability to simultaneously run and monitor multiple Selenium instances.
63+
>> * Provides a keyword-based testing approach that Selenium does not have.
64+
>> * Can produce test reports that record actions taken during the test.
65+
>> * Can execute tests remotely through TCP/IP.
66+
>> * Offers a CLI mode for Web Testing.
67+
---
68+
### API Testing components
69+
> Simple way to testing HTTP/S & Soap \
70+
> Wrapper for Requests package, designed for those with experience using Requests. \
71+
> Send HTTP/S and SOAP requests with a simple line of code or keyword. \
72+
> Detailed information on Requests and Responses. \
73+
> Solves problems such as:
74+
>> * Detailed testing reports on Requests and Responses.
75+
>> * Testing for SOAP protocol.
76+
>> * Data comparison for each Request.
77+
>> * API Testing in pure CLI mode.
78+
---
79+
### Load & Stress Testing components
80+
> Locust Wrapper \
81+
> Wrapper for Locust, simplifying complex Locust configurations. \
82+
> Solves problems:
83+
>> * Checking Requests & Response for each load test
84+
>> * Load testing for SOAP protocols
85+
>> * Comparison of numerical values for each load test
86+
>> * Detailed load test reports for each test.
987
---
1088

1189
### Features
1290

13-
* ITE GUI for beginner
14-
* GUI testing (use AutoControl)
15-
* API testing (use APITestka)
16-
* Web testing (use WebRunner)
17-
* Loading testing (use LoadDensity)
18-
* Multi test task runner (multi process)
19-
* you can run multi testing on same time
20-
* open log window to check testing result
21-
* Send mail when testing failure (need to setting mail)
91+
> * ITE GUI for beginner
92+
> * GUI testing (use AutoControl)
93+
> * API testing (use APITestka)
94+
> * Web testing (use WebRunner)
95+
> * Loading testing (use LoadDensity)
96+
> * Multi test task runner (multi process)
97+
> * you can run multi testing on same time
98+
> * open log window to check testing result
99+
> * Send mail when testing failure (need to setting mail)
22100
23101
---
24102

‎pyproject.toml‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,12 +1,12 @@
1-
# Rename to dev stable version
1+
# Rename to dev version
22
# This is dev version
33
[build-system]
44
requires = ["setuptools>=61.0"]
55
build-backend = "setuptools.build_meta"
66

77
[project]
8-
name = "integration_testing_environment"
9-
version = "0.0.18"
8+
name = "integration_testing_environment_dev"
9+
version = "0.0.19"
1010
authors = [
1111
{ name = "JE-Chen", email = "zenmailman@gmail.com" },
1212
]

‎stable.toml‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ build-backend = "setuptools.build_meta"
66

77
[project]
88
name = "integration_testing_environment"
9-
version = "0.0.12"
9+
version = "0.0.18"
1010
authors = [
1111
{ name = "JE-Chen", email = "zenmailman@gmail.com" },
1212
]

0 commit comments

Comments
 (0)