← Back to Test Runner
What is this?
The Test Runner is a web app for validating that all 15 Wrike automation workflows (rebuilt in n8n) work correctly. It has 75 test checks across 12 sections. You work through each test by making changes in Wrike and recording whether the expected result happened.
Test Checks
75 tests grouped by section (A–L). Each has setup instructions, an action to perform, and an expected result.
Wrike Context
Each test includes a "Where in Wrike" panel showing the exact task/story/phase to use. No guessing.
n8n Activity Feed
Live sidebar showing n8n workflow executions as they happen. Confirms automations are firing.
Auto-Save & Export
Results save to your browser automatically. Export as CSV or Markdown when done.
Getting Started
2
Click START SESSION in the top-right header. This starts polling n8n for live workflow executions.
3
Open Wrike in another browser tab. Navigate to Media Buying → TEST — Automation Validation. This is your test environment.
Your progress saves automatically. You can close the browser and come back anytime — all results are stored locally. You can work across multiple sessions and days.
Running a Test
1
Click a test row to expand it. You'll see the Setup, Expected Result, and a blue "Where in Wrike" box showing exactly which task to use.
2
Follow the Wrike context. The blue box tells you the navigation path, story name, action name, and any prep steps (like assigning yourself). Do the prep first.
3
Perform the action described in the test (e.g., "Change Action to In Progress") on the specific Wrike task.
4
Wait 10–15 seconds, then check whether the expected result happened in Wrike. Glance at the n8n activity feed to confirm the workflow fired.
5
Mark the result. Click Pass, Fail, Skip, or Untested. If it failed, type what actually happened in the Actual Result field.
6
Move to the next test. Sequential tests (e.g., A2.1 through A2.5) use the same Wrike tasks — don't create new ones.
Using the Interface
Header bar
CSV / MD — Export your results as a spreadsheet or Markdown reportRESET — Clear all results and start over (asks for confirmation)START SESSION / END SESSION — Controls the n8n activity feed pollingn8n — Toggle the activity feed sidebar on/off
Test sections
- Click a section header (A–L) to collapse/expand it
- Each section shows a progress counter (e.g.,
3/13)
- Use the search bar to find specific tests by ID, name, or keyword
- Use the status filter buttons (All, Untested, Pass, Fail, Skip) to focus on specific results
Expanded test row
Click any test row to expand it. The expanded view shows:
- Setup — What needs to be in place before testing
- Expected Result — What should happen
- Where in Wrike (blue box) — Exact navigation path, story/action names, and prep instructions
- Status buttons — Untested / Pass / Fail / Skip
- Actual Result — What actually happened (fill in on failure)
- Notes — Any observations
- Tester — Your name
- Task URL — Paste the Wrike task URL for reference
n8n Activity Feed
- Shows live n8n workflow executions after you start a session
- Green
success = workflow ran fine. Red error = something went wrong.
- Each entry shows the workflow name, status, timestamp, and duration
- If you make a change in Wrike and nothing appears here, the webhook may not have fired
Timing
Single cascade (Action → Story) — 5–15 seconds
Multi-level cascade (Action → Story → Gate) — 15–30 seconds
Full cascade (Action → Story → Gate → Phase → Project) — 60–90 seconds
Validator revert — 5–15 seconds
Scheduled jobs (Sections I, J) — Runs at specific AEST times. Set up the day before.
Important Rules
- All testing happens inside TEST — Automation Validation in Media Buying. Do NOT test in real client folders.
- Template Actions have dates but no assignee. You must assign yourself before most tests (the "Where in Wrike" box will remind you).
- Sequential tests (e.g., A2.1–A2.5) use the same tasks. "Same as A2.1" means keep using the tasks from that step.
- If something fails, record what actually happened rather than trying to fix it.
When You're Done
- Click
CSV and MD to export both formats
- Send the exports to Aaron via Slack
- Click
END SESSION
- Do NOT delete the TEST folder — Aaron may need to inspect tasks
Thank you for testing! If you have any questions, reach out to Aaron.
Back to Test Runner