Skip to content

Commit cad3f5f

Browse files
authored
Merge pull request #5 from GuardianUI/jem-review-2
Feedback
2 parents 70165f0 + e2c056d commit cad3f5f

25 files changed

+55
-69
lines changed

README.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -1,12 +1,16 @@
11
# GuardianUI Overview
22

3-
[GuardianUI](https://www.guardianui.com/) is an end-to-end testing and monitoring platform for web3 apps. We offer a suite of products designed to improve frontend security and UX in the crypto space, including our open source testing framework - [GuardianTest](platform/readme/).
3+
[GuardianUI](https://www.guardianui.com/) is an end-to-end testing and monitoring platform for web3 apps. We offer a suite of products designed to improve frontend security and UX in the crypto space, including our open source testing framework - [GuardianTest](platform/guardian-test/).
4+
5+
## Mission
6+
7+
Our mission is simple. We aim to make it easy for web3 developers to create reliable, robust, and safe applications for users. We are currently focused on improving E2E testing and monitoring.
48

59
## GuardianUI Ecosystem
610

7-
### [GuardianTest](platform/readme/)
11+
### [GuardianTest](platform/guardian-test/)
812

9-
The GuardianUI Test framework ("GuardianTest") is an open source E2E testing framework developed to suit the demands of crypto organizations and developers.
13+
The GuardianUI Test framework ("GuardianTest") is an open source E2E testing framework developed to suit the demands of crypto projects and developers.
1014

1115
It extends the popular [Playwright](https://playwright.dev/) testing framework so developers can easily:
1216

@@ -24,12 +28,8 @@ Our monitoring system lets users run their tests written with the GuardianTest f
2428

2529
Learn more about our monitoring product and the frontend exploits it can help detect [here](https://www.guardianui.com/).
2630

27-
### [StoryCheck](platform/storycheck-beta.md)
31+
### [StoryCheck (BETA)](platform/storycheck-beta.md)
2832

2933
StoryCheck is a system designed to drastically reduce the difficulty of writing end-to-end tests and aims to make it a process non-developers can also participate in. At its core, it converts text into automatically executed test code. It does so by taking markdown formatted user stories with steps written in natural language as input. Then it parses the text and executes steps in a virtual web browser (via Playwright) closely emulating the actions of a real user. It uses [RefExp GPT](https://huggingface.co/spaces/GuardianUI/ui-refexp-click) to predict UI element coordinates given a referring expression.
3034

3135
Learn more about StoryCheck and how you can integrate it into your testing workflow [here](https://github.com/GuardianUI/storycheck).
32-
33-
## Mission
34-
35-
Our mission is simple. We aim to make it easy for web3 developers to create reliable, robust, and safe applications for users. We are currently focused on improving E2E testing and monitoring.

SUMMARY.md

Lines changed: 23 additions & 23 deletions
Original file line numberDiff line numberDiff line change
@@ -6,35 +6,35 @@
66

77
## Platform
88

9-
* [GuardianTest](platform/readme/GuardianTest.md)
10-
* [Overview](platform/readme/overview/README.md)
11-
* [Key Benefits](platform/readme/overview/key-benefits.md)
12-
* [Framework Roadmap](platform/readme/overview/framework-roadmap.md)
13-
* [Supported Chains](platform/readme/overview/supported-chains.md)
14-
* [End-to-End Testing Overview](platform/readme/overview/end-to-end-testing-overview.md)
15-
* [Getting Started](platform/readme/getting-started/README.md)
16-
* [Installation](platform/readme/getting-started/installation.md)
17-
* [Writing Tests](platform/readme/getting-started/writing-your-first-e2e-test.md)
18-
* [Running Tests](platform/readme/getting-started/running-tests.md)
19-
* [Test Examples](platform/readme/getting-started/test-examples.md)
20-
* [API](platform/readme/api/README.md)
21-
* [GUI](platform/readme/api/gui.md)
22-
* [Playwright](platform/readme/api/playwright.md)
23-
* [Integrations](platform/readme/integrations/README.md)
24-
* [CI/CD Integrations](platform/readme/integrations/ci-cd-integrations.md)
25-
* [Monitoring Integrations](platform/readme/integrations/monitoring-integrations.md)
26-
* [Guides](platform/readme/guides/README.md)
27-
* [Actions](platform/readme/guides/actions.md)
28-
* [Mocking APIs](platform/readme/guides/mocking-apis.md)
29-
* [Mocking Subgraph](platform/readme/guides/mocking-subgraph.md)
30-
* [Screenshots](platform/readme/guides/screenshots.md)
9+
* [GuardianTest](platform/guardian-test/GuardianTest.md)
10+
* [Overview](platform/guardian-test/overview/README.md)
11+
* [Key Benefits](platform/guardian-test/overview/key-benefits.md)
12+
* [Framework Roadmap](platform/guardian-test/overview/framework-roadmap.md)
13+
* [Supported Chains](platform/guardian-test/overview/supported-chains.md)
14+
* [End-to-End Testing Overview](platform/guardian-test/overview/end-to-end-testing-overview.md)
15+
* [Getting Started](platform/guardian-test/getting-started/README.md)
16+
* [Installation](platform/guardian-test/getting-started/installation.md)
17+
* [Writing Tests](platform/guardian-test/getting-started/writing-your-first-e2e-test.md)
18+
* [Running Tests](platform/guardian-test/getting-started/running-tests.md)
19+
* [Test Examples](platform/guardian-test/getting-started/test-examples.md)
20+
* [API](platform/guardian-test/api/README.md)
21+
* [GUI](platform/guardian-test/api/gui.md)
22+
* [Playwright](platform/guardian-test/api/playwright.md)
23+
* [Integrations](platform/guardian-test/integrations/README.md)
24+
* [CI/CD Integrations](platform/guardian-test/integrations/ci-cd-integrations.md)
25+
* [Monitoring Integrations](platform/guardian-test/integrations/monitoring-integrations.md)
26+
* [Guides](platform/guardian-test/guides/README.md)
27+
* [Actions](platform/guardian-test/guides/actions.md)
28+
* [Mocking APIs](platform/guardian-test/guides/mocking-apis.md)
29+
* [Mocking Subgraph](platform/guardian-test/guides/mocking-subgraph.md)
30+
* [Screenshots](platform/guardian-test/guides/screenshots.md)
3131
* [Continuous Monitoring](platform/continuous-monitoring/README.md)
3232
* [Monitoring](platform/continuous-monitoring/monitoring/README.md)
3333
* [How We Run Checks](platform/continuous-monitoring/monitoring/how-we-run-checks.md)
3434
* [Check Results](platform/continuous-monitoring/monitoring/check-results.md)
3535
* [How We Store Data](platform/continuous-monitoring/monitoring/how-we-store-data.md)
3636
* [Browser Checks](platform/continuous-monitoring/browser-checks/README.md)
37-
* [Writing Tests](platform/readme/getting-started/writing-your-first-e2e-test.md)
37+
* [Writing Tests](platform/guardian-test/getting-started/writing-your-first-e2e-test.md)
3838
* [Request Custom Test Writing](platform/continuous-monitoring/browser-checks/request-custom-test-writing.md)
3939
* [Submitting Tests for Monitoring](platform/continuous-monitoring/browser-checks/submitting-tests-for-monitoring.md)
4040
* [Alerts](platform/continuous-monitoring/alerts/README.md)

platform/continuous-monitoring/browser-checks/README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -18,9 +18,9 @@ Your browser checks should verify:
1818

1919
The combination of automated interactions and assertions leads to confidence that your app works as expected.
2020

21-
GuardianUI's monitoring system uses tests written in [GuardianTest](https://app.gitbook.com/o/aEzOvP1ODgbzLwqZ2irE/s/6blK04TyOYOkA5ZEQW4b/\~/changes/15/platform/readme), a custom modification to the popular [Playwright](https://github.com/microsoft/playwright) framework, to power your browser checks. 
21+
GuardianUI's monitoring system uses tests written in [GuardianTest](/platform/guardian-test/), a custom modification to the popular [Playwright](https://github.com/microsoft/playwright) framework, to power your browser checks. 
2222

23-
For examples of valid browser checks and instructions for how to create them, see [Writing Tests](broken-reference) and [Test Examples](../../readme/getting-started/test-examples.md).
23+
For examples of valid browser checks and instructions for how to create them, see [Writing Tests](/platform/guardian-test/getting-started/writing-your-first-e2e-test/) and [Test Examples](/platform/guardian-test/getting-started/test-examples/.
2424

2525
{% hint style="info" %}
2626
Valid GuardianTest scripts are the foundation of a valid browser check. If the script passes, your check passes. If the script fails, your check fails.

platform/readme/GuardianTest.md renamed to platform/guardian-test/README.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ description: >-
77

88
# GuardianTest
99

10-
GuardianTest is an open source E2E testing framework developed to suit the demands of crypto organizations and developers.
10+
GuardianTest is an [open source](https://github.com/GuardianUI/GuardianTest) E2E testing framework developed to suit the demands of crypto projects and developers.
1111

1212
It extends the popular [Playwright](https://playwright.dev/) testing framework so developers can easily:
1313

@@ -18,4 +18,3 @@ It extends the popular [Playwright](https://playwright.dev/) testing framework s
1818
* Mock ERC20 balances and allowances
1919
* Validate target contract addresses from app interactions
2020
* Perform any other actions or validation Playwright offers
21-
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.

platform/readme/getting-started/installation.md renamed to platform/guardian-test/getting-started/installation.md

Lines changed: 11 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -2,12 +2,12 @@
22

33
## Dependencies
44

5-
### Installing Node.js
5+
### Node.js
66

77
* Check if you already have Node installed by opening a terminal or command prompt instance and executing `node -v`. You should see a version number in the return.
88
* If you do not have Node already installed, go to [Node.js](https://nodejs.org/en/download) and select the version associated with your operating system.
99

10-
### Installing Foundry
10+
### Foundry
1111

1212
Check if you already have [Anvil](https://github.com/foundry-rs/foundry/tree/master/anvil) installed through Foundry by opening a terminal or command prompt instance and executing `anvil -V`. You should see a version number in the return. If you do not, follow one of the guides below.
1313

@@ -19,29 +19,27 @@ Check if you already have [Anvil](https://github.com/foundry-rs/foundry/tree/mas
1919
* **CI**
2020
* [Installation for CI](https://book.getfoundry.sh/getting-started/installation#installing-for-ci-in-github-action)
2121

22-
## Installing GuardianTest
22+
### GuardianTest
2323

2424
You can install GuardianTest using either npm or yarn:
2525

26-
**npm**
26+
#### NPM
2727

28-
`npm install @guardianui/test`
28+
`npm install --save-dev @guardianui/test`
2929

30-
**yarn**
30+
#### Yarn
3131

32-
`yarn add @guardianui/test`
32+
`yarn add --dev @guardianui/test`
3333

34-
## Installing Playwright Browsers
34+
### Playwright Browsers
3535

3636
`npx playwright install`
3737

38-
39-
4038
## Configuring the Framework
4139

4240
### Playwright Config
4341

44-
At your repo's top-level directory create a file called `playwright.config.ts`
42+
At your repo's top-level directory create a file called `playwright.config.ts`.
4543

4644
If you already are using Playwright and already have a `playwright.config.ts`, just add `/.*gui\.(js|ts|mjs)/` to the `testMatch` entry to make sure Playwright recognizes our tests.
4745

@@ -155,20 +153,16 @@ const config: PlaywrightTestConfig = {
155153
export default config;
156154
```
157155

158-
159-
160156
### env
161157

162158
At your repo's top-level directory create another file called `.env` or if you already have one add the following to your existing `.env`. Comment out whichever line you do not use with a `#` at the start.
163159

164-
```
160+
```bash
165161
# Must fill in one of these API keys, do not need both
166162
GUARDIAN_UI_INFURA_API_KEY=
167163
GUARDIAN_UI_ALCHEMY_API_KEY=
168164
```
169165

170-
171-
172166
### package.json
173167

174168
To be able to run tests, add the following to your app's `package.json` scripts section:
@@ -177,8 +171,6 @@ To be able to run tests, add the following to your app's `package.json` scripts
177171
"test:gui": "npx playwright test --project=chromium --headed"
178172
```
179173

180-
181-
182174
### Tests Folder
183175

184-
Create a folder called `tests` to house your GuardianTest tests in
176+
Create a folder called `tests` to house your GuardianTest tests in.
File renamed without changes.

0 commit comments

Comments
 (0)