使用场景大纲处理 Gherkin 中的大字符串

Question

我将 Behat 用于 BDD 并使用 Scenario Outlines，因此我可以轻松地对其他数据进行相同的测试。但是我遇到了大文本的问题。请参见下面的示例：

Scenario Outline: create a thing
  When I click on "New"
  Then I should be at "/thing/new"
  When I fill in "title" with <title>
  When I fill in "description" with "description"
  When I click on "save"
  Then I should be at "/things"
  Then I should see <title> in the list
  When I click on <title>
  Then I should see <title>
  Then I should see <description>

  Examples:
    | title          | description |
    | "My new thing" | "a very large string a very large string a very large string a very large string a very large string a very large string a very large string a very large string a very large string a very large string a very large string a very large string a very large string a very large string a very large string" |

您可以想象，如果有更多大文本或更多类型的值，这可能会很烦人。有解决方案吗？例如使用变量？可能是这样的：

$myvar = "a very large string a very large string a very large string a very large string a very large string a very large string a very large string a very large string a very large string a very large string a very large string a very large string a very large string a very large string a very large string"

Scenario Outline: create a thing
  When I click on "New"
  Then I should be at "/thing/new"
  When I fill in "title" with <title>
  When I fill in "description" with "description"
  When I click on "save"
  Then I should be at "/things"
  Then I should see <title> in the list
  When I click on <title>
  Then I should see <title>
  Then I should see <description>

  Examples:
    | title          | description |
    | "My new thing" | $myvar      |

Answer 1

如果是我，我会写出更高级别的场景。你描述的需求是什么？如果是“事物”最多可以有 500 个字符（或其他）的描述，那么就这样说，而不是使用任意长字符串：

When I fill in "description" with a 500 character description
....
Then the new thing should have a description 500 characters long
 And the new thing's description should match the description entered

然后，您的 When 步骤实现可以生成 500 个字符的 Lorem Ipsum 数据，将其输入表单并将其存储在 Scenario 上下文中以供稍后检查。

它不漂亮但是：

1. 它比随机的“长字符串”更好地描述了需求
2. 它使功能文件更干净、更简洁

可能值得应用相同的“我描述的是什么要求？”对场景的其余部分也有疑问。这里发生了很多事情，我个人会分成多个场景。

Answer 2

我不认为我们可以像你用$myvar 举例说明的那样有变量。如果 James McCalden 的建议不适合您，将内容放在外部文件中可能与您的 $myvar 建议非常接近，例如：

Scenario Outline: create a thing
  When I ... 
  ...
  Then I should see <title>
  Then I should see <description>

  Examples:
    | title          | description |
    | "My new thing" | /mydir/myvar.txt |

那么 test resources 目录中的/mydir/myvar.txt 将包含：

a very large string a very large string a very large string a very large string a very large string a very large string a very large string a very large string a very large string a very large string a very large string a very large string a very large string a very large string a very large string

最后在你的步骤课上：

 @Then("Then I should see (.+)")
 public void thenISouldSee(String param) {
       param = process(param);
       ...
 }

 private String process(String parameter) throws IOException, URISyntaxException {
       return parameter.charAt(0) == '/' ? readFile(parameter) : parameter;
 }

 private String readFile(String dir) throws IOException, URISyntaxException {
        File file = new File(BrandsContentManagementSteps.class.getResource(dir).toURI());
        return FileUtils.readFileToString(file, StandardCharsets.UTF_8);
 }

请注意，FileUtils 需要导入 apache commons.io。