Commit 780d5cd8 authored by Walmyr Lima's avatar Walmyr Lima

Simplify the burndown end-to-end test

By leaving the project fabrication to the milestone fabrication
since it creates it by default if none is provided.
parent c02c1c9e
...@@ -5,15 +5,8 @@ module QA ...@@ -5,15 +5,8 @@ module QA
describe 'Burndown chart' do describe 'Burndown chart' do
include ::QA::Support::Dates include ::QA::Support::Dates
let(:project) do
Resource::Project.fabricate_via_api! do |project|
project.name = 'project-to-test-burndown-chart'
end
end
let(:milestone) do let(:milestone) do
QA::EE::Resource::ProjectMilestone.fabricate_via_api! do |m| QA::EE::Resource::ProjectMilestone.fabricate_via_api! do |m|
m.project = project
m.title = 'v1' m.title = 'v1'
m.start_date = current_date_yyyy_mm_dd m.start_date = current_date_yyyy_mm_dd
m.due_date = next_month_yyyy_mm_dd m.due_date = next_month_yyyy_mm_dd
...@@ -25,8 +18,8 @@ module QA ...@@ -25,8 +18,8 @@ module QA
weight_of_two = 2 weight_of_two = 2
create_issue('Issue 1', project, milestone, weight_of_two) create_issue('Issue 1', milestone.project, milestone, weight_of_two)
create_issue('Issue 2', project, milestone, weight_of_two) create_issue('Issue 2', milestone.project, milestone, weight_of_two)
end end
it 'shows burndown chart on milestone page' do it 'shows burndown chart on milestone page' do
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment