BigW Consortium Gitlab
We perform a ton of expensive setup in this spec, via both `before` and `let!`. When we use `skip` inside an `it` block, rather than skipping the block entirely via `xit`, we still perform this expensive setup, only to do absolutely nothing with it, resulting in wasted time. Minutes, in this case. Further, these specs have been sitting in our test suite for about seven months now, so the likelihood of them being addressed soon seems low.
Name |
Last commit
|
Last update |
---|---|---|
.. | ||
filtered_search | Loading commit data... | |
award_emoji_spec.rb | Loading commit data... | |
award_spec.rb | Loading commit data... | |
bulk_assignment_labels_spec.rb | Loading commit data... | |
create_branch_merge_request_spec.rb | Loading commit data... | |
create_issue_for_discussions_in_merge_request_spec.rb | Loading commit data... | |
create_issue_for_single_discussion_in_merge_request_spec.rb | Loading commit data... | |
form_spec.rb | Loading commit data... | |
gfm_autocomplete_spec.rb | Loading commit data... | |
group_label_sidebar_spec.rb | Loading commit data... | |
issue_detail_spec.rb | Loading commit data... | |
issue_sidebar_spec.rb | Loading commit data... | |
markdown_toolbar_spec.rb | Loading commit data... | |
move_spec.rb | Loading commit data... | |
note_polling_spec.rb | Loading commit data... | |
notes_on_issues_spec.rb | Loading commit data... | |
spam_issues_spec.rb | Loading commit data... | |
todo_spec.rb | Loading commit data... | |
update_issues_spec.rb | Loading commit data... | |
user_uses_slash_commands_spec.rb | Loading commit data... |