Commit 4bbc19c
committed
🧑💻 Output path to feature file and source for steps
Problem:
Working with BDD tests can be challenging in large repositories
because it is difficult to find the implementation of steps. Patterns
of text substitution and multi-line strings make simple greps for step
definitions insufficient.
Solution:
Rather than outputting either the step location or the feature file
location, we will instead output the feature file location and
optionally the step definition location if available (uses $Given,
$When, $Then)1 parent 1f802e4 commit 4bbc19c
1 file changed
+17
-10
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
592 | 592 | | |
593 | 593 | | |
594 | 594 | | |
595 | | - | |
| 595 | + | |
596 | 596 | | |
597 | 597 | | |
598 | | - | |
599 | | - | |
600 | | - | |
601 | | - | |
602 | | - | |
603 | | - | |
| 598 | + | |
604 | 599 | | |
605 | 600 | | |
606 | | - | |
607 | | - | |
608 | | - | |
| 601 | + | |
| 602 | + | |
| 603 | + | |
| 604 | + | |
| 605 | + | |
| 606 | + | |
| 607 | + | |
| 608 | + | |
| 609 | + | |
| 610 | + | |
| 611 | + | |
| 612 | + | |
| 613 | + | |
| 614 | + | |
| 615 | + | |
609 | 616 | | |
610 | 617 | | |
611 | 618 | | |
| |||
0 commit comments