[UITEST-2] FOLIO integration test framework Created: 16/Aug/17  Updated: 20/Aug/18  Resolved: 20/Aug/18

Status: Closed
Project: stripes-testing
Components: None
Affects versions: None
Fix versions: None

Type: Task Priority: P3
Reporter: Niels Erik Nielsen Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: sprint20
Σ Remaining Estimate: 30 minutes Remaining Estimate: Not Specified
Σ Time Spent: 1 week, 2 days, 2 hours, 50 minutes Time Spent: 1 week, 45 minutes
Σ Original Estimate: Not Specified Original estimate: Not Specified

Issue links:
Relates
relates to FOLIO-798 Parameterize npm repo for ui-testing ... Closed
relates to STCOR-74 Add non-visible foundations versions ... Closed
relates to STRIPES-461 document ID/naming scheme Closed
relates to UICHKOUT-1 Deepen test coverage of CheckOut Blocked
relates to UITEST-7 Find approach for creating/collecting... Closed
Sub-tasks:
Key
Summary
Type
Status
Assignee
UITEST-3 Move Items-only and Users-only tests ... Sub-task Closed Niels Erik Nielsen  
UITEST-4 Create hook in in ui-testing for invo... Sub-task Closed Niels Erik Nielsen  
UITEST-5 Document how to write module tests to... Sub-task Closed Niels Erik Nielsen  
UITEST-6 Document how to run module tests from... Sub-task Closed Niels Erik Nielsen  
Sprint:

 Description   

Considering

  • test frameworks
  • how to make tests resilient (unique identifiers etc)
  • how to keep test suites in sync with UI changes
  • how to enlist developers in maintenance of test cases
  • documentation on automated testing


 Comments   
Comment by Niels Erik Nielsen [ 17/Aug/17 ]

Tests living in ui-checkout, with a hook in ui-testing to run them as part of a platform-wide test suite.

Hooks in ui-testing:

https://github.com/folio-org/ui-testing/commit/71336fbf9dfb8ebad8a42716970bd52e1a9617c4

Actual test scripts in ui-checkout:

https://github.com/folio-org/ui-checkout/commit/3a8ce94419af19e6714f94ae2569f8ee484c687f

Comment by Niels Erik Nielsen [ 22/Aug/17 ]

The main issue with stability of the tests seems to be related to timing - especially when trying to reproduce test results running the test from a local machine against the sites on AWS.

Timeouts can occur due to spikes in the download time for the bundle - affecting the login actions.

Timing issues occur in the login page too, apparently due to the page being rendered multiple times. Thus the tests apply a wait time, since checking for expected elements in the page is no guarantee that the page will not re-render and thus loose already entered un/pw for instance.

Settings is another area where there seems to be some heavy reloading (patron groups for instance).

Today I've added waits around Settings operations and made timeouts and waits configurable, since the behavior very much depends on the environment the tests are run in.

Comment by Niels Erik Nielsen [ 01/Sep/17 ]

Added nightmare options as command line arguments to 'test-module' script.

Generated at Thu Feb 08 23:08:17 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.