Behave Modern Report — Demo

Started 2026-06-29 12:22:45 · Duration 1m 1s · 5 features · 25 scenarios

Failed

Passed

56.0% pass rate

Failed

7 with error

Skipped

scenarios

Undefined

scenarios

Pending

scenarios

Total

5 features · 108 steps

Rules

2 failed

Avg duration

2.44s

slowest step 1.18s

Attachments

0 logs

Errors

AssertionError

Passed 14 Failed 7 Undefined 4 56.0% pass rate

❌ *Behave Modern Report — Demo*
*7 scenario(s) failed*
📊 25 scenarios · 5 features · 108 steps
⏱️ Duration 1m 1s · Avg 2.44s
📈 Pass rate 56.0%

🔴 Failed: 7
🟢 Passed: 14
🟡 Undefined: 4
💥 Most common error: AssertionError
📜 Rules: 2 (2 failed)

Status distribution

Scenarios over time

Duration histogram

Slowest scenarios

Tags with worst pass rate

Error distribution

Features

5 features · 25 scenarios

Behavior of the checkout subsystem including rules.

features/Checkout.feature:20
1. Then the user opens the dashboard 356ms
2. And the cart contains 5 items 916ms
3. Given the cart contains 5 items 733ms

features/Checkout.feature:4
1. When the user opens the dashboard 814ms
2. Given the user opens the dashboard 41ms
  AssertionError
```
Traceback (most recent call last):
  File "features/steps/example.py", line 42, in step_impl
    assert response.status_code == 200
AssertionError: Expected 200 but got 500
```
3. When the cart contains 1 items 243ms
features/Checkout.feature:8
1. Then the response payload matches the schema 412ms
2. When the user opens the dashboard 459ms
3. Then the user opens the dashboard 877ms
4. Given the cart contains 2 items 355ms
5. When the user opens the dashboard 795ms
6. Given the response payload matches the schema 337ms

features/Checkout.feature:12
1. Then the cart contains 2 items 764ms
2. When the response payload matches the schema 328ms
3. When the user opens the dashboard 279ms
4. Then the user opens the dashboard 257ms
features/Checkout.feature:16
1. And they click the buy button 322ms
  AssertionError
```
Traceback (most recent call last):
  File "features/steps/example.py", line 42, in step_impl
    assert response.status_code == 200
AssertionError: Expected 200 but got 500
```
2. Then the cart contains 7 items 482ms
3. When the user opens the dashboard 908ms
4. When the response payload matches the schema 718ms
5. And the cart contains 8 items 305ms

features/login.feature:10

Scenario Outline Login with valid credentials
1. Given the username is "alice" 100ms
2. When the user logs in 200ms
3. Then the dashboard is shown 100ms
Examples

username password

alice secret1

bob secret2

carol secret3
features/login.feature:20

Scenario Outline Login with invalid credentials
1. Given the username is "eve" 100ms
2. When the user logs in 200ms
3. Then the error is shown 100ms
Examples

username password

eve wrong

mallory bad

username	password
alice	secret1
bob	secret2
carol	secret3

username	password
eve	wrong
mallory	bad

Behavior of the authentication subsystem.

features/Authentication.feature:4
1. Given the API returns 200 291ms
  AssertionError
```
Traceback (most recent call last):
  File "features/steps/example.py", line 42, in step_impl
    assert response.status_code == 200
AssertionError: Expected 200 but got 500
```
2. Given the user opens the dashboard 1.17s
3. When the cart contains 8 items 202ms
features/Authentication.feature:8
1. And the user opens the dashboard 301ms
2. Then they click the login button 708ms
3. Given they click the buy button 86ms
4. Then they click the login button 338ms
5. When the cart contains 3 items 694ms
  AssertionError
```
Traceback (most recent call last):
  File "features/steps/example.py", line 42, in step_impl
    assert response.status_code == 200
AssertionError: Expected 200 but got 500
```
features/Authentication.feature:12
1. And the user opens the dashboard 810ms
2. Given the user opens the dashboard 302ms
3. And they click the login button 338ms
features/Authentication.feature:16
1. Given the user opens the dashboard 1.16s
2. When the response payload matches the schema 260ms
3. Given the user opens the dashboard 1.18s
4. And the cart contains 7 items 796ms
5. When they click the login button 1.16s
  AssertionError
```
Traceback (most recent call last):
  File "features/steps/example.py", line 42, in step_impl
    assert response.status_code == 200
AssertionError: Expected 200 but got 500
```
6. Given the user opens the dashboard 65ms
features/Authentication.feature:20
1. Given the response payload matches the schema 148ms
2. When the cart contains 1 items 103ms
3. Then the API returns 200 290ms
features/Authentication.feature:24
1. Given the user opens the dashboard 647ms
2. Then the user opens the dashboard 1.06s
3. Then the cart contains 8 items 846ms
4. Given the API returns 200 1.12s
5. When the user opens the dashboard 892ms
features/Authentication.feature:28
1. Then the API returns 200 1.09s
2. Given the API returns 200 58ms
3. When they click the buy button 891ms
4. And the user opens the dashboard 95ms
features/Authentication.feature:32
1. And the API returns 200 441ms
2. Then the user opens the dashboard 428ms
3. And they click the buy button 1.04s
4. And the API returns 200 940ms
5. When the user opens the dashboard 462ms

Behavior of the reporting subsystem.

features/Reporting.feature:4
1. When the response payload matches the schema 397ms
2. Then the response payload matches the schema 817ms
3. Then the API returns 200 218ms
4. Given the API returns 200 876ms
5. And the user opens the dashboard 465ms
features/Reporting.feature:8
1. When the user opens the dashboard 1.14s
2. Then the API returns 200 611ms
3. Then the cart contains 5 items 157ms
features/Reporting.feature:12
1. Then the response payload matches the schema 944ms
2. And they click the submit button 616ms
3. Given the cart contains 9 items 406ms
4. Then they click the login button 34ms
5. And the response payload matches the schema 500ms
6. When the response payload matches the schema 483ms
features/Reporting.feature:16
1. When the response payload matches the schema 65ms
2. Given the response payload matches the schema 803ms
3. Then the response payload matches the schema 998ms
features/Reporting.feature:20
1. And the API returns 200 531ms
2. When the API returns 200 1.07s
3. When the response payload matches the schema 834ms
4. Given the API returns 200 653ms
5. Given the response payload matches the schema 1.09s
features/Reporting.feature:24
1. Then the cart contains 7 items 898ms
2. When the API returns 200 526ms
3. And they click the submit button 1.01s
4. Given the user opens the dashboard 773ms
5. And the API returns 200 458ms
6. And the response payload matches the schema 338ms

Behavior of the settings subsystem.

features/Settings.feature:4
1. When the user opens the dashboard 906ms
2. When they click the login button 156ms
3. When the API returns 200 206ms
features/Settings.feature:8
1. Given the response payload matches the schema 1.13s
2. Given the user opens the dashboard 838ms
3. Given the API returns 200 642ms
4. Given the user opens the dashboard 1.02s
features/Settings.feature:12
1. When the cart contains 3 items 1.16s
  AssertionError
```
Traceback (most recent call last):
  File "features/steps/example.py", line 42, in step_impl
    assert response.status_code == 200
AssertionError: Expected 200 but got 500
```
2. And the cart contains 7 items 326ms
3. Given they click the submit button 902ms
4. And the response payload matches the schema 1.02s
5. And the API returns 200 412ms
6. Given the user opens the dashboard 293ms
features/Settings.feature:16
1. Given the response payload matches the schema 832ms
2. Then the cart contains 9 items 416ms
3. Then the API returns 200 371ms
4. Given the API returns 200 148ms
5. When the response payload matches the schema 335ms
6. Then the API returns 200 277ms

Rules

All Gherkin Rules grouped by feature.

features/Checkout.feature:4
1. When the user opens the dashboard 814ms
2. Given the user opens the dashboard 41ms
  AssertionError
```
Traceback (most recent call last):
  File "features/steps/example.py", line 42, in step_impl
    assert response.status_code == 200
AssertionError: Expected 200 but got 500
```
3. When the cart contains 1 items 243ms
features/Checkout.feature:8
1. Then the response payload matches the schema 412ms
2. When the user opens the dashboard 459ms
3. Then the user opens the dashboard 877ms
4. Given the cart contains 2 items 355ms
5. When the user opens the dashboard 795ms
6. Given the response payload matches the schema 337ms

features/Checkout.feature:12
1. Then the cart contains 2 items 764ms
2. When the response payload matches the schema 328ms
3. When the user opens the dashboard 279ms
4. Then the user opens the dashboard 257ms
features/Checkout.feature:16
1. And they click the buy button 322ms
  AssertionError
```
Traceback (most recent call last):
  File "features/steps/example.py", line 42, in step_impl
    assert response.status_code == 200
AssertionError: Expected 200 but got 500
```
2. Then the cart contains 7 items 482ms
3. When the user opens the dashboard 908ms
4. When the response payload matches the schema 718ms
5. And the cart contains 8 items 305ms

Scenarios

All scenarios across all features.

features/Checkout.feature:4
1. When the user opens the dashboard 814ms
2. Given the user opens the dashboard 41ms
  AssertionError
```
Traceback (most recent call last):
  File "features/steps/example.py", line 42, in step_impl
    assert response.status_code == 200
AssertionError: Expected 200 but got 500
```
3. When the cart contains 1 items 243ms
features/Checkout.feature:8
1. Then the response payload matches the schema 412ms
2. When the user opens the dashboard 459ms
3. Then the user opens the dashboard 877ms
4. Given the cart contains 2 items 355ms
5. When the user opens the dashboard 795ms
6. Given the response payload matches the schema 337ms
features/Checkout.feature:12
1. Then the cart contains 2 items 764ms
2. When the response payload matches the schema 328ms
3. When the user opens the dashboard 279ms
4. Then the user opens the dashboard 257ms
features/Checkout.feature:16
1. And they click the buy button 322ms
  AssertionError
```
Traceback (most recent call last):
  File "features/steps/example.py", line 42, in step_impl
    assert response.status_code == 200
AssertionError: Expected 200 but got 500
```
2. Then the cart contains 7 items 482ms
3. When the user opens the dashboard 908ms
4. When the response payload matches the schema 718ms
5. And the cart contains 8 items 305ms
features/Checkout.feature:20
1. Then the user opens the dashboard 356ms
2. And the cart contains 5 items 916ms
3. Given the cart contains 5 items 733ms
features/login.feature:10

Scenario Outline Login with valid credentials
1. Given the username is "alice" 100ms
2. When the user logs in 200ms
3. Then the dashboard is shown 100ms
Examples

username password

alice secret1

bob secret2

carol secret3
features/login.feature:20

Scenario Outline Login with invalid credentials
1. Given the username is "eve" 100ms
2. When the user logs in 200ms
3. Then the error is shown 100ms
Examples

username password

eve wrong

mallory bad
features/Authentication.feature:4
1. Given the API returns 200 291ms
  AssertionError
```
Traceback (most recent call last):
  File "features/steps/example.py", line 42, in step_impl
    assert response.status_code == 200
AssertionError: Expected 200 but got 500
```
2. Given the user opens the dashboard 1.17s
3. When the cart contains 8 items 202ms
features/Authentication.feature:8
1. And the user opens the dashboard 301ms
2. Then they click the login button 708ms
3. Given they click the buy button 86ms
4. Then they click the login button 338ms
5. When the cart contains 3 items 694ms
  AssertionError
```
Traceback (most recent call last):
  File "features/steps/example.py", line 42, in step_impl
    assert response.status_code == 200
AssertionError: Expected 200 but got 500
```
features/Authentication.feature:12
1. And the user opens the dashboard 810ms
2. Given the user opens the dashboard 302ms
3. And they click the login button 338ms
features/Authentication.feature:16
1. Given the user opens the dashboard 1.16s
2. When the response payload matches the schema 260ms
3. Given the user opens the dashboard 1.18s
4. And the cart contains 7 items 796ms
5. When they click the login button 1.16s
  AssertionError
```
Traceback (most recent call last):
  File "features/steps/example.py", line 42, in step_impl
    assert response.status_code == 200
AssertionError: Expected 200 but got 500
```
6. Given the user opens the dashboard 65ms
features/Authentication.feature:20
1. Given the response payload matches the schema 148ms
2. When the cart contains 1 items 103ms
3. Then the API returns 200 290ms
features/Authentication.feature:24
1. Given the user opens the dashboard 647ms
2. Then the user opens the dashboard 1.06s
3. Then the cart contains 8 items 846ms
4. Given the API returns 200 1.12s
5. When the user opens the dashboard 892ms
features/Authentication.feature:28
1. Then the API returns 200 1.09s
2. Given the API returns 200 58ms
3. When they click the buy button 891ms
4. And the user opens the dashboard 95ms
features/Authentication.feature:32
1. And the API returns 200 441ms
2. Then the user opens the dashboard 428ms
3. And they click the buy button 1.04s
4. And the API returns 200 940ms
5. When the user opens the dashboard 462ms
features/Reporting.feature:4
1. When the response payload matches the schema 397ms
2. Then the response payload matches the schema 817ms
3. Then the API returns 200 218ms
4. Given the API returns 200 876ms
5. And the user opens the dashboard 465ms
features/Reporting.feature:8
1. When the user opens the dashboard 1.14s
2. Then the API returns 200 611ms
3. Then the cart contains 5 items 157ms
features/Reporting.feature:12
1. Then the response payload matches the schema 944ms
2. And they click the submit button 616ms
3. Given the cart contains 9 items 406ms
4. Then they click the login button 34ms
5. And the response payload matches the schema 500ms
6. When the response payload matches the schema 483ms
features/Reporting.feature:16
1. When the response payload matches the schema 65ms
2. Given the response payload matches the schema 803ms
3. Then the response payload matches the schema 998ms
features/Reporting.feature:20
1. And the API returns 200 531ms
2. When the API returns 200 1.07s
3. When the response payload matches the schema 834ms
4. Given the API returns 200 653ms
5. Given the response payload matches the schema 1.09s
features/Reporting.feature:24
1. Then the cart contains 7 items 898ms
2. When the API returns 200 526ms
3. And they click the submit button 1.01s
4. Given the user opens the dashboard 773ms
5. And the API returns 200 458ms
6. And the response payload matches the schema 338ms
features/Settings.feature:4
1. When the user opens the dashboard 906ms
2. When they click the login button 156ms
3. When the API returns 200 206ms
features/Settings.feature:8
1. Given the response payload matches the schema 1.13s
2. Given the user opens the dashboard 838ms
3. Given the API returns 200 642ms
4. Given the user opens the dashboard 1.02s
features/Settings.feature:12
1. When the cart contains 3 items 1.16s
  AssertionError
```
Traceback (most recent call last):
  File "features/steps/example.py", line 42, in step_impl
    assert response.status_code == 200
AssertionError: Expected 200 but got 500
```
2. And the cart contains 7 items 326ms
3. Given they click the submit button 902ms
4. And the response payload matches the schema 1.02s
5. And the API returns 200 412ms
6. Given the user opens the dashboard 293ms
features/Settings.feature:16
1. Given the response payload matches the schema 832ms
2. Then the cart contains 9 items 416ms
3. Then the API returns 200 371ms
4. Given the API returns 200 148ms
5. When the response payload matches the schema 335ms
6. Then the API returns 200 277ms

username	password
alice	secret1
bob	secret2
carol	secret3

username	password
eve	wrong
mallory	bad

Results

All scenarios as a compact results table.

Status	Feature	Rule	Scenario	Duration	Tags
Failed	Checkout	Payment required	Scenario 1: permissions	1.10s	@payment
Undefined	Checkout	Payment required	Scenario 2: reporting	3.23s	@payment
Passed	Checkout	Shipping options	Scenario 3: permissions	1.63s	@shipping
Failed	Checkout	Shipping options	Scenario 4: permissions	2.73s	@shipping
Passed	Checkout	-	Scenario 5: checkout	2.00s	@regression@nightly
Passed	User Login	-	Outline example: Login with valid credentials	400ms	@login@outline
Failed	User Login	-	Outline example: Login with invalid credentials	400ms	@login@outline
Failed	Authentication	-	Scenario 1: permissions	1.67s	@regression@nightly@wip
Failed	Authentication	-	Scenario 2: checkout	2.13s	@api@regression@smoke
Passed	Authentication	-	Scenario 3: checkout	1.45s
Failed	Authentication	-	Scenario 4: API contract	4.63s	@smoke
Undefined	Authentication	-	Scenario 5: API contract	540ms	@wip
Passed	Authentication	-	Scenario 6: checkout	4.56s	@ui@nightly
Passed	Authentication	-	Scenario 7: checkout	2.13s
Passed	Authentication	-	Scenario 8: login flow	3.31s	@regression@wip@api
Passed	Reporting	-	Scenario 1: permissions	2.77s	@ui
Passed	Reporting	-	Scenario 2: API contract	1.91s	@wip@regression@ui
Undefined	Reporting	-	Scenario 3: checkout	2.98s
Passed	Reporting	-	Scenario 4: permissions	1.87s	@regression@api@nightly
Passed	Reporting	-	Scenario 5: permissions	4.18s
Passed	Reporting	-	Scenario 6: API contract	4.00s	@smoke@api
Passed	Settings	-	Scenario 1: permissions	1.27s
Passed	Settings	-	Scenario 2: API contract	3.63s
Failed	Settings	-	Scenario 3: API contract	4.11s	@nightly@regression@api
Undefined	Settings	-	Scenario 4: checkout	2.38s	@smoke@nightly

Tag	Scenarios	Passed	Failed	Skip/Undef/Pend	Pass rate	Duration
@authentication	8	4	3	1	50.0%	20.41s
@regression	7	4	3	0	57.1%	17.00s
@nightly	6	3	2	1	50.0%	16.59s
@checkout	5	2	2	1	40.0%	10.70s
@api	5	3	2	0	60.0%	15.42s
@smoke	4	1	2	1	25.0%	13.14s
@wip	4	2	1	1	50.0%	7.42s
@settings	4	2	1	1	50.0%	11.39s
@login	2	1	1	0	50.0%	800ms
@outline	2	1	1	0	50.0%	800ms
@payment	2	0	1	1	0.0%	4.33s
@shipping	2	1	1	0	50.0%	4.36s
@reporting	6	5	0	1	83.3%	17.71s
@ui	3	3	0	0	100.0%	9.24s

Statistics

Raw metrics and distribution tables.

Scenarios

Passed

Failed

Pass rate

56.0%

Duration

1m 1s

Avg scenario

2.44s

Status distribution

Status	Count	Percentage
Passed	14	56.0%
Failed	7	28.0%
Undefined	4	16.0%

Duration percentiles

Min	Avg	P50	P90	P95	Max
400ms	2.44s	2.13s	4.15s	4.48s	4.63s

Per-feature summary

Feature	Status	Scenarios	Passed	Failed	Duration	Avg	Pass rate
Authentication	Failed	8	4	3	20.41s	2.55s	50.0%
Checkout	Failed	5	2	2	10.70s	2.14s	40.0%
Settings	Failed	4	2	1	11.39s	2.85s	50.0%
User Login	Failed	2	1	1	800ms	400ms	50.0%
Reporting	Undefined	6	5	0	17.71s	2.95s	83.3%

Error distribution

Exception type	Count
`AssertionError`	6

Behave Modern Report — Demo

Status distribution

Scenarios over time

Duration histogram

Slowest scenarios

Tags with worst pass rate

Error distribution

Features

Checkout

User Login

Authentication

Reporting

Settings

Rules

Scenarios

Results

Tags

Tag details

Statistics

Status distribution

Duration percentiles

Per-feature summary

Error distribution

Environment

Runtime

Git

Environment variables

Extra