可以在單個小黃瓜場景中有多組Given/When/Then

Question

我正在編寫一個驗證測試，在希望測試基於初始操作的Web應用的UI中的多個更改的小黃瓜中。下面是一個示例：

 Scenario: Cancel editing a new text asset 
      Given the user "test_user@fakedomain.com" is logged in 
      When the user navigates to "/build/" 
      And the user clicks the "Sandbox" link 
      And the user inputs "Test story for canceling editing of a new text asset" for the "title" field 
      And the user inputs "Test User" for the "byline" field 
      And the user inputs "My summary, so exciting!" for the "summary" textarea 
      And the user clicks on "Untitled Section" in the section list 
      And the user clicks the "Text" icon in the "center" container 
      And the user inputs the following text in the rich text editor: 
        """ 
        Test text for asset. This is cool. 
        """ 
      And the user clicks the "cancel" button 
      Then the following text is not present: 
        """ 
        Test text for asset. This is cool. 
        """ 
      And the "Image" icon is present 
      And the "Text" icon is present 
      When the user refreshes the browser 
      And the user clicks on "Untitled Section" in the section list 
      Then the following text is not present: 
        """ 
        Test text for asset. This is cool. 
        """ 
      When the user opens the asset drawer 
      Then the following text is not present: 
        """ 
        Test text for asset. This is cool. 
        """ 

請注意，有多組When/Then步驟來測試初始操作的響應。雖然大多數步驟的實現忽略前綴關鍵字，並且我非常確定我可以運行此測試，但有沒有更好的方法來測試不同的結果？使用相同的設置但不同的「Then」語句編寫多個場景是否更好？

Answer 1

請記住，您應該一次只測試一個行爲/功能。 經驗法則是，你應該使用只有當步驟：

Given some state before action 
    And some other state before action 
    ... 
When only one action 
Then assert correct output 
    And assert correct output 
    ... 

你看 - 如果，沒有任何ANDS下，當只有一行。如果您使用許多When步驟，則可以創建測試腳本，而不是規範。您的測試很難理解，並且您會注意到當底層實現發生更改時，您會添加越來越多的步驟。

您還需要保持潛在的邏輯隱藏，因爲您不想每次更改無關的內容時都更改它。例如：

而用戶輸入「我的總結，太令人興奮了！」 「摘要」 textarea

如果將摘要字段從textarea更改爲輸入類型，該怎麼辦？你必須改變場景（維護噩夢）或讓你的場景撒謊（比沒有場景更糟糕）。你應該寫：

When the user describes it as "so exciting!" 

但仍然，整個場景的結構是不好的。問自己這個問題：我想檢查什麼？如果我是那個想了解該功能的業務邏輯的人，我想看到的東西，如：

Scenario: Cancel editing a new text asset 
    Given I edit the Sandbox details with some data 
    When I cancel editing 
    Then Sandox details should be empty 

這就是它！

如何實現它？移動所有不相關的邏輯更深入，使用PageObject pattern等。並閱讀約Specification By Example