mdan-cli 2.2.0 → 2.3.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/.mcp.json +46 -0
- package/AGENTS.md +246 -0
- package/README.md +30 -5
- package/agents/test.md +60 -2
- package/cli/mdan.js +129 -6
- package/install.sh +30 -167
- package/integrations/mcp.md +153 -0
- package/package.json +4 -2
- package/phases/04-verify.md +9 -3
- package/templates/prompts/README.md +108 -0
- package/templates/prompts/dev-agent.yaml +85 -0
- package/templates/prompts/orchestrator.yaml +97 -0
- package/templates/prompts.json +81 -0
- package/templates/tests/evaluations/README.md +80 -0
- package/templates/tests/evaluations/classification_eval.md +136 -0
- package/templates/tests/evaluations/rag_eval.md +116 -0
- package/templates/tests/scenarios/README.md +62 -0
- package/templates/tests/scenarios/basic_authentication.test.md +82 -0
- package/templates/tests/scenarios/user_registration.test.md +107 -0
|
@@ -0,0 +1,107 @@
|
|
|
1
|
+
# Scenario: User Registration
|
|
2
|
+
|
|
3
|
+
> Test conversation flow for new user signup
|
|
4
|
+
|
|
5
|
+
## Metadata
|
|
6
|
+
|
|
7
|
+
| Field | Value |
|
|
8
|
+
|-------|-------|
|
|
9
|
+
| scenario_name | user_registration |
|
|
10
|
+
| version | 1.0.0 |
|
|
11
|
+
| agent | Dev Agent |
|
|
12
|
+
| framework | [Jest/Pytest/Playwright] |
|
|
13
|
+
| estimated_duration | 45s |
|
|
14
|
+
|
|
15
|
+
## Description
|
|
16
|
+
|
|
17
|
+
Test that the registration system handles new user creation, validation, and confirmation correctly.
|
|
18
|
+
|
|
19
|
+
## Preconditions
|
|
20
|
+
|
|
21
|
+
- User is not logged in
|
|
22
|
+
- Database is clean or has known state
|
|
23
|
+
- Email service is mocked or test-ready
|
|
24
|
+
|
|
25
|
+
## Script
|
|
26
|
+
|
|
27
|
+
### Test Case 1: Successful Registration
|
|
28
|
+
|
|
29
|
+
```
|
|
30
|
+
USER: I want to create a new account
|
|
31
|
+
AGENT: [Should prompt for registration details]
|
|
32
|
+
USER:
|
|
33
|
+
- email: newuser@example.com
|
|
34
|
+
- password: SecurePass123!
|
|
35
|
+
- name: New User
|
|
36
|
+
AGENT: [Should validate and create account]
|
|
37
|
+
-> VERIFY: user created in database
|
|
38
|
+
-> VERIFY: confirmation email sent
|
|
39
|
+
-> VERIFY: success message shown
|
|
40
|
+
-> VERIFY: user NOT automatically logged in (email verification required)
|
|
41
|
+
```
|
|
42
|
+
|
|
43
|
+
### Test Case 2: Duplicate Email
|
|
44
|
+
|
|
45
|
+
```
|
|
46
|
+
USER: I want to register
|
|
47
|
+
AGENT: [Should prompt for details]
|
|
48
|
+
USER: email: existing@example.com (already in DB), password: Test123!
|
|
49
|
+
AGENT: [Should reject duplicate]
|
|
50
|
+
-> VERIFY: error message about email already exists
|
|
51
|
+
-> VERIFY: no account created
|
|
52
|
+
-> VERIFY: password NOT in error message (security)
|
|
53
|
+
```
|
|
54
|
+
|
|
55
|
+
### Test Case 3: Invalid Email Format
|
|
56
|
+
|
|
57
|
+
```
|
|
58
|
+
USER: I want to register
|
|
59
|
+
AGENT: [Should prompt for details]
|
|
60
|
+
USER: email: not-an-email, password: Test123!
|
|
61
|
+
AGENT: [Should validate format]
|
|
62
|
+
-> VERIFY: error about invalid email format
|
|
63
|
+
-> VERIFY: no account created
|
|
64
|
+
```
|
|
65
|
+
|
|
66
|
+
### Test Case 4: Weak Password
|
|
67
|
+
|
|
68
|
+
```
|
|
69
|
+
USER: I want to register
|
|
70
|
+
AGENT: [Should prompt for details]
|
|
71
|
+
USER: email: valid@example.com, password: 123
|
|
72
|
+
AGENT: [Should reject weak password]
|
|
73
|
+
-> VERIFY: error about password requirements
|
|
74
|
+
-> VERIFY: no account created
|
|
75
|
+
```
|
|
76
|
+
|
|
77
|
+
### Test Case 5: Email Confirmation
|
|
78
|
+
|
|
79
|
+
```
|
|
80
|
+
USER: I've received my confirmation email
|
|
81
|
+
AGENT: [Should provide link or code input]
|
|
82
|
+
USER: Confirmation code: ABC123
|
|
83
|
+
AGENT: [Should verify and activate account]
|
|
84
|
+
-> VERIFY: account marked as active
|
|
85
|
+
-> VERIFY: user can now log in
|
|
86
|
+
```
|
|
87
|
+
|
|
88
|
+
## Success Criteria
|
|
89
|
+
|
|
90
|
+
- [ ] Valid registration creates account
|
|
91
|
+
- [ ] Duplicate email is rejected securely
|
|
92
|
+
- [ ] Invalid email format is rejected
|
|
93
|
+
- [ ] Weak passwords are rejected
|
|
94
|
+
- [ ] Email confirmation activates account
|
|
95
|
+
- [ ] Password requirements are enforced
|
|
96
|
+
- [ ] No sensitive data in error messages
|
|
97
|
+
|
|
98
|
+
## Security Checks
|
|
99
|
+
|
|
100
|
+
- Password not logged or exposed in errors
|
|
101
|
+
- Email enumeration prevention
|
|
102
|
+
- Rate limiting on registration attempts
|
|
103
|
+
- SQL injection prevention in form inputs
|
|
104
|
+
|
|
105
|
+
## Notes
|
|
106
|
+
|
|
107
|
+
This scenario covers the complete registration flow. Adjust validation rules based on project requirements.
|