Commit fdfb7d3c authored by Luke Duncalfe's avatar Luke Duncalfe

Fix jira_service_spec

Previously this test asserted that `expected_new_issue_url` was only
a path. `JiraService#new_issue_url_with_predefined_fields` does return
the full URL, but previously the `:jira_service` factory had a `nil`
URL if they were built and not saved. The factory is now consistent,
so the error in this test surfaced.
parent dc000c6f
......@@ -384,7 +384,7 @@ RSpec.describe JiraService do
allow(jira_service).to receive(:vulnerabilities_issuetype).and_return('10001')
end
let(:expected_new_issue_url) { '/secure/CreateIssueDetails!init.jspa?pid=11223&issuetype=10001&summary=Special+Summary%21%3F&description=%2AID%2A%3A+2%0A_Issue_%3A+%21' }
let(:expected_new_issue_url) { "#{jira_service.url}/secure/CreateIssueDetails!init.jspa?pid=11223&issuetype=10001&summary=Special+Summary%21%3F&description=%2AID%2A%3A+2%0A_Issue_%3A+%21" }
subject(:new_issue_url) { jira_service.new_issue_url_with_predefined_fields("Special Summary!?", "*ID*: 2\n_Issue_: !") }
......
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