### Manual Installation from Source with Cargo

Source: https://github.com/jikkenio/jikken/blob/main/README.md

Clone the Jikken repository and install it manually using Cargo. This method is suitable for developers who want to build from source.

```bash
$ git clone https://github.com/jikkenio/jikken.git
$ cd jikken
$ cargo install
```

--------------------------------

### Install Jikken with Cargo (Git Repository)

Source: https://github.com/jikkenio/jikken/blob/main/README.md

Install Jikken directly from its Git repository using Cargo. This is useful for installing development versions or specific branches.

```bash
$ cargo install --git http://www.github.com/jikkenio/jikken
```

--------------------------------

### Install Jikken with Chocolatey

Source: https://github.com/jikkenio/jikken/blob/main/README.md

Install Jikken using Chocolatey on Windows systems. Ensure Chocolatey is installed and configured on your system.

```bash
$ choco install jikken
```

--------------------------------

### Install Jikken with Cargo (Crates.io)

Source: https://github.com/jikkenio/jikken/blob/main/README.md

Install Jikken using Cargo if you have the Rust toolchain installed and want to use the latest stable version from crates.io.

```bash
$ cargo install jikken
```

--------------------------------

### Install Jikken with Homebrew

Source: https://github.com/jikkenio/jikken/blob/main/README.md

Use this command if you are on macOS or Linux and use Homebrew for package management.

```bash
$ brew tap jikkenio/jikken
$ brew install jikken
```

--------------------------------

### Run Tests with Jikken CLI

Source: https://github.com/jikkenio/jikken/blob/main/README.md

Execute tests in the current directory. Jikken automatically finds and runs tests defined in .jkt files. Use the -r flag to recurse into subdirectories.

```bash
$ jk run
Jikken found 2 tests.
Running Test (1/2) `Test 1` Iteration(1/1) Runtime(5ms) ... PASSED!
Running Test (2/2) `Test 2` Iteration(1/1) Runtime(102ms) ... PASSED!
Running Test (2/2) `Test 2` Iteration(2/1) Runtime(80ms) ... PASSED!
```

```bash
$ jk run
Jikken found 2 tests.
Running Test (1/2) `Fetch Auth Credentials` Iteration(1/1) Runtime(5) ... PASSED!
Running Test (2/2) `My API Test` Iteration(1/2) Runtime(103ms) ... PASSED!
Running Test (2/2) `My API Test` Iteration(2/2) Runtime(75ms) ... PASSED!
```

--------------------------------

### TOML Configuration for Jikken CLI

Source: https://github.com/jikkenio/jikken/blob/main/README.md

Defines settings and global variables for Jikken CLI in a .jikken TOML file. Supports 'continueOnFailure', 'environment', and 'apiKey' settings, along with global variables like 'newUrl' and 'oldUrl'.

```toml
continueOnFailure=true
environment="qa"
apiKey="52adb38c-a0e4-438d-bff3-aa83a1a9a8ba"

newUrl="https://localhost:5001"
oldUrl="https://localhost:5002"
```

--------------------------------

### Setting Global Variables via Environment Variables

Source: https://github.com/jikkenio/jikken/blob/main/README.md

Demonstrates how to set global variables for Jikken CLI using environment variables. These can override values in the .jikken file or define new ones. The prefix 'JIKKEN_GLOBAL_' is required.

```bash
EXPORT JIKKEN_GLOBAL_newUrl=https://localhost:5001
EXPORT JIKKEN_GLOBAL_oldUrl=https://localhost:5002
jk
```

--------------------------------

### Dry Run Tests with Jikken CLI

Source: https://github.com/jikkenio/jikken/blob/main/README.md

Simulate test execution without actually running them. This command prints a report of the steps that would occur, including requests, headers, and validation checks.

```bash
$ jk dryrun
Jikken found 3 tests.
Dry Run Test (1/3) `Test 1` Iteration(1/1)
request: POST https://api.jikken.io/v1/test_login
request_headers:
-- Content-Type: application/json
request_body: { "username":"testuser", "password":"password" }
validate request_status with defined status: 200
attempt to extract value from response: token = valueOf(auth.token)
Dry Run Test (2/3) `Check Status` Iteration(1/1)
request: GET https://api.jikken.io/v1/test_status
request_headers:
-- Authorization: ${token}
validate request_status with defined status: 200
Dry Run Test (3/3) `Compare StatusV2 and StatusV1` Iteration(1/1)
request: GET https://api.jikken.io/v2/test_status
request_headers:
-- Authorization: ${token}
validate request_status with defined status: 200
prune fields from response_body
filter: user.lastActivity
comparison mode
compare_request: GET https://api.jikken.io/v1/test_status
compare_headers:
-- Authorization: ${token}
validate request_status_code matches compare_request_status_code
prune fields from compare_response_body
filter: user.lastActivity
validate filtered response_body matches filtered compare_response_body
```

--------------------------------

### Filter Tests by Multiple Tags (OR)

Source: https://github.com/jikkenio/jikken/blob/main/README.md

Run tests that have any of the provided tags. Use the --tags-or flag to include tests matching at least one of the specified tags.

```bash
$ jk run -t foo -t bar --tags-or
Jikken found 8 tests
```

--------------------------------

### Filter Tests by Multiple Tags (AND)

Source: https://github.com/jikkenio/jikken/blob/main/README.md

Execute tests that possess all specified tags. This allows for more precise test selection by requiring multiple conditions to be met.

```bash
$ jk run -t foo -t bar
Jikken found 2 tests.
```

--------------------------------

### Filter Tests by Single Tag

Source: https://github.com/jikkenio/jikken/blob/main/README.md

Run only tests that have a specific tag. This is useful for executing a subset of tests, such as regression tests.

```bash
$ jk run -t regression
Jikken found 5 tests.
```

=== COMPLETE CONTENT === This response contains all available snippets from this library. No additional content exists. Do not make further requests.