Skip to content

Tests covering the Cells demos

Andy Hohenner requested to merge Cells_Demo_Tests into master

Description of the test

This MR covers work done in Create tests for Cells Demos 2 & 3 (gitlab-org/quality/quality-engineering/team-tasks#2096 - closed)

It contains test that demonstrate that the Tenant Scale Demo functionality still works. The tests are currently blocked from running in CI as it's expected that they will currently be run locally only.

How to set up and validate locally

Stand up two Cells in GDK per the how to instructions

From the qa directory:

bundle install
export WEBDRIVER_HEADLESS=false # If you'd like to watch the test in action
export QA_GITLAB_URL="http://gdk.test:3000" # Only needed if GDK is not running on http://127.0.0.1:3000
export CELL1_URL="http://localhost:3000/" # Only needed if Cell1 is not running on http://gdk.test:3000/
export CELL2_URL="http://localhost:3001/" # Only needed if Cell1 is not running on http://gdk.test:3001/
bundle exec rspec qa/specs/features/browser_ui/9_data_stores/cells/

If you just want to run the Demo2 script:

WEBDRIVER_HEADLESS=false bundle exec rspec qa/specs/features/browser_ui/9_data_stores/cells/demo2_spec.rb

If you just want to run the Demo3 script:

WEBDRIVER_HEADLESS=false bundle exec rspec qa/specs/features/browser_ui/9_data_stores/cells/demo3_spec.rb

Related issues

Checklist

  • Confirm the test has a testcase: tag linking to an existing test case in the test case project.
  • Note if the test is intended to run in specific scenarios. If a scenario is new, add a link to the MR that adds the new scenario.
  • Follow the end-to-end tests style guide and best practices.
  • Use the appropriate RSpec metadata tag(s).
  • Most resources will be cleaned up via the general cleanup task. Check that is successful, or ensure resources are cleaned up in the test:
    • New resources have api_get_path and api_delete_path implemented if possible.
    • If any resource cannot be deleted in the general delete task, make sure it is ignored.
    • If any resource cannot be deleted in the general delete task, remove it in the test (e.g., in an after block).
  • Ensure that no transient bugs are hidden accidentally due to the usage of waits and reloads.
  • Verify the tags to ensure it runs on the desired test environments.
  • If this MR has a dependency on another MR, such as a GitLab QA MR, specify the order in which the MRs should be merged.
  • (If applicable) Create a follow-up issue to document the special setup necessary to run the test: ISSUE_LINK
  • If the test requires an admin's personal access token, ensure that the test passes on your local environment with and without the GITLAB_QA_ADMIN_ACCESS_TOKEN provided.
Edited by Andy Hohenner

Merge request reports