| var expect = require("chai").expect; | |
| var walk_tests = require("./walk_xunit_tests.js").walk_tests; | |
| var util = require('util'); | |
| describe("walk_tests", function() { | |
| let input = `<?xml version="1.0" encoding="UTF-8"?> | |
| <testsuites> | |
| <testsuite name="SuiteA" errors="0" skipped="1" tests="3" failures="1"> | |
| <testcase classname="Class A" name="test1" time="0.006" status="run"/> |
| { | |
| "LABEL": { | |
| "name": "PR title needs jira ticket", | |
| "color": "CC00CC" | |
| }, | |
| "CHECKS": { | |
| "alwaysPassCI": false, | |
| "prefixes": [ "Bump " ], | |
| "regexp": "\\[[A-Z]{2,}-\\d+(,\\s*[A-Z]{2,}-\\d+)*\\]", | |
| "regexpFlags": "", |
Most teams run BDD scenarios as integration tests through the UI or API. It seems logical: Gherkin describes high-level behavior, so run high-level tests.
But what if that assumption costs you 10 minutes or even hours of feedback time, brittle infrastructure, and constant debugging?
I propose an approach that flips the script: BDD at unit level.