@qadet/runner 0.3.1 → 0.4.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +8 -43
- package/package.json +2 -2
- package/qadet.mjs +2177 -68645
- package/explorer.md +0 -108
- package/repairer.md +0 -7
package/README.md
CHANGED
|
@@ -1,63 +1,28 @@
|
|
|
1
1
|
# Qadet Runner
|
|
2
2
|
|
|
3
|
-
|
|
3
|
+
Runs the browser tests you start in Qadet, in Chrome on this computer. The AI and the tests live in your Qadet workspace; the runner needs no AI key of its own.
|
|
4
4
|
|
|
5
5
|
## Requirements
|
|
6
6
|
|
|
7
7
|
- Node.js 22 or newer
|
|
8
8
|
- Google Chrome
|
|
9
|
-
- A
|
|
9
|
+
- A runner token from your workspace's **Runner tokens** page
|
|
10
10
|
|
|
11
11
|
## Install
|
|
12
12
|
|
|
13
|
+
Copy the install command from **Runner tokens** in Qadet. It names the runner version your workspace needs, for example:
|
|
14
|
+
|
|
13
15
|
```sh
|
|
14
16
|
npm install --global @qadet/runner@0.3.1
|
|
15
17
|
```
|
|
16
18
|
|
|
17
|
-
|
|
19
|
+
When Qadet needs a newer runner, it shows the command to update.
|
|
18
20
|
|
|
19
21
|
## Connect and run
|
|
20
22
|
|
|
21
|
-
Connect this computer to your Qadet workspace:
|
|
22
|
-
|
|
23
|
-
```sh
|
|
24
|
-
qadet connect
|
|
25
|
-
```
|
|
26
|
-
|
|
27
|
-
The guided flow asks for the workspace URL and a runner token, verifies the connection, and offers to start the runner. Token input is hidden and does not need to be placed in shell history. You can still supply the URL as `qadet connect https://qadet.example`; scripts can supply both the URL and token.
|
|
28
|
-
|
|
29
|
-
Verify the saved connection at any time:
|
|
30
|
-
|
|
31
|
-
```sh
|
|
32
|
-
qadet status
|
|
33
|
-
```
|
|
34
|
-
|
|
35
|
-
This shows the workspace, authenticated user, organization, installed runner version, and whether a compatible runner using this token has checked in recently. It never displays the token. Verification does not start the runner or mark it online.
|
|
36
|
-
|
|
37
|
-
To start a previously connected runner:
|
|
38
|
-
|
|
39
|
-
```sh
|
|
40
|
-
qadet agent
|
|
41
|
-
```
|
|
42
|
-
|
|
43
|
-
The connection is stored in the current user's configuration directory. To remove it, run `qadet disconnect`.
|
|
44
|
-
|
|
45
|
-
## Other commands
|
|
46
|
-
|
|
47
|
-
```sh
|
|
48
|
-
qadet explore https://app.example/login "Sign in and verify the dashboard loads"
|
|
49
|
-
qadet replay checkout
|
|
50
|
-
qadet snapshot https://app.example/login
|
|
51
|
-
```
|
|
52
|
-
|
|
53
|
-
Run `qadet help` for the available commands. Qadet stores run history and saved tests in the web application.
|
|
54
|
-
|
|
55
|
-
## Publish a release
|
|
56
|
-
|
|
57
|
-
Set the new version in `runner/package.json`, then publish locally with:
|
|
58
|
-
|
|
59
23
|
```sh
|
|
60
|
-
|
|
24
|
+
qadet connect # once: asks for your workspace address and token, and checks them
|
|
25
|
+
qadet agent # whenever you want to run tests; stop it with Ctrl+C
|
|
61
26
|
```
|
|
62
27
|
|
|
63
|
-
|
|
28
|
+
`qadet status` checks the connection, and `qadet disconnect` removes it. The token is never shown or stored in your shell history.
|
package/package.json
CHANGED