Story #15335

[Workbench2] Integration testing

Added by Eric Biagiotti 6 months ago. Updated 3 months ago.

Status:
New
Priority:
Normal
Assigned To:
-
Category:
-
Target version:
Start date:
Due date:
% Done:

0%

Estimated time:
Story points:
-

Description

Test Workbench 2 features that need to interact with other Arvados components.

  • Should use run-tests.sh start_services()
  • Need a framework for headless browser testing via something like puppeteer
  • Write tests for features that have interaction with other components, such as upload/download, login, account linking

Related issues

Related to Arvados - Story #15333: [Epic] Workbench2 has reached feature parity with Workbench, so that that latter can be deprecatedNew

Related to Arvados - Bug #15321: [workbench2] Test run, package building & deploy integrationNew

Blocks Arvados - Story #15581: [Workbench2] Improve error handling and reportingNew

History

#1 Updated by Eric Biagiotti 6 months ago

  • Related to Story #15333: [Epic] Workbench2 has reached feature parity with Workbench, so that that latter can be deprecated added

#2 Updated by Eric Biagiotti 6 months ago

  • Subject changed from Workbench 2 integration testing to [Workbench2] Integration testing

#3 Updated by Tom Morris 4 months ago

  • Target version set to To Be Groomed

#4 Updated by Peter Amstutz 3 months ago

  • Description updated (diff)

#5 Updated by Peter Amstutz 3 months ago

  • Related to Bug #15321: [workbench2] Test run, package building & deploy integration added

#6 Updated by Tom Morris 3 months ago

  • Blocks Story #15581: [Workbench2] Improve error handling and reporting added

#7 Updated by Eric Biagiotti 3 months ago

  • Description updated (diff)

Some framework options:

  • Selenium/Webdriver (Selenium2) - Supports writing cross-browser tests in Java (and other languages on the JVM including Groovy), Python, Ruby, and C#

Also available in: Atom PDF