我有一个包含8-9行步骤的特性文件A,它涵盖了一个场景。现在,我需要将特性文件A作为特性文件B中的后台步骤,将步骤数减少到3-4。
我的方法:
功能文件B中的
特征文件A:
Feature: I want to create an event
Background: User is Logged In
Given a logged in user
Scenario: Creating an event
Given I select event
And I add event details
And I add start and end time
Then Timings will be added successfully
When I add ticket information and continue
And Publish my event
Then I verify event will be created successfully特征文件B
Feature: Place an order
Background: Event is created
Given a logged in user
When I select event and fill in required details
Then event should be published我担心的是重复。我使用特性文件A作为特征文件B中的后台步骤,减少了步骤数,但从功能上说,这两个特性文件都测试着相同的特性。
如果可能的话,请提出更好的方法。谢谢
发布于 2021-08-11 15:29:17
因此,从根本上说,如果压缩的步骤也正确地传递信息,那么使用助手方法减少步骤数是应该做的事情。下面是一个例子(这里也不需要帮手),这将是一个很好的用例。
Given I have a party of 2/1/0 # This means adults/children/infants
And the child is under 12
And I am flexible on my flights
And I am going to Spain
When I search for flightsGiven I have Spanish flights displayed # You could also add the pax in here if you wanted现在,如果您想使用帮助方法,这也很好,但是您需要记住,黄瓜主要是一种鼓励协作以及在同一位置提供文档、测试和规范的工具。因此,一旦你试图使你的线条干涸,想想实际上你是否只想把线条“压缩”下来。
即
Given('I am {int} years old') do |age|
@person.age = age
end
Given('my name is {word}') |name|
@person.name = name
end
Given('my hometown is {string}') |hometown|
@person.location = hometown
end会变成
Given('I am {word}, {int} years old from {string}') |name, age, hometown|
@person.name = name
@person.age = age
@person.location = hometown
end希望这些技巧中的一些会给你一些想法。
https://stackoverflow.com/questions/68744143
复制相似问题