<!--- The issue should have the following: - The relative path of the failing spec file in the title, e.g. if the login test fails, include `qa/specs/ui/login/log_in_spec.rb` in the title. This is required so that existing issues can easily be found by searching for the spec file. - If the issue is about multiple test failures, include the path for each failing spec file in the description. - A link to the failing job. - The stack trace from the job's logs in the "Stack trace" section below. - A screenshot (if available), and HTML capture (if available), in the "Screenshot / HTML page" section below. ---> # QA Failure ## Summary ### Stack trace ```ruby 1) User adds more SaaS GitLab Duo Pro seats when for a Premium subscription behaves like successful SaaS Duo Pro purchase displays in CustomersDot and GitLab Failure/Error: expect(usage_page).to have_seats(used: 0, total: total_duo_pro_quantity, wait_for_zuora: true) QA::Helper::Errors::ReachedMaxRetriesError: Expected GitLab Duo seats to match 0 / 7 Shared Example Group: "successful SaaS Duo Pro purchase" called from ./spec/ui/purchase/add_duo_pro_seats_spec.rb:39 Shared Example Group: "when purchasing seats" called from ./spec/ui/purchase/add_duo_pro_seats_spec.rb:38 Shared Example Group: "when SaaS subscription already exists" called from ./spec/ui/purchase/add_duo_pro_seats_spec.rb:37 # ./runtime/retrier.rb:75:in `retry_until' # ./vendor/gitlab/page/component/duo.rb:27:in `has_seats?' # ./spec/shared_examples/duo_pro_successful_saas_purchase.rb:19:in `block (3 levels) in <module:QA>' # ./page/base.rb:22:in `perform' # ./spec/shared_examples/duo_pro_successful_saas_purchase.rb:17:in `block (2 levels) in <module:QA>' ``` ### Screenshot / HTML page  ### Possible fixes