Details
Description
It would be nice to see ui-testing have no dependencies on Stripes UI modules. It does so today because ui-testing is acting both as a test framework as well as the integration platform of sorts.
Tests that span multiple apps would be better kept within a platform which defines those apps under test, like folio-testing-platform. This would leave ui-testing's responsibility as a testing framework only.
The advantage of this separation is that ui-testing can then be incorporated into other tools, like Stripes-CLI without pulling down the entire app ecosystem. Further, by having platform tests kept with a platform, we can define and maintain tests that may be unique to different platforms. Organizationally, this is much like how we have app tests that are kept with each app.
TestRail: Results
Attachments
Issue Links
- blocks
-
FOLIO-1266 Reorganizing CI and nightly with platform-core and -complete
-
- Closed
-
- relates to
-
STCLI-63 Support running tests against existing instance
-
- Closed
-
-
UITEST-39 Add coverage functionality to stripes-testing method
-
- Closed
-
-
UITEST-47 relocate the "framework-only" to stripes-testing repo
-
- Closed
-
-
FOLIO-1450 Revise FOLIO release and deployment process
-
- Open
-
-
STCLI-5 Resolve CLI ui-testing dependency issues
-
- Closed
-
-
UXPROD-1132 Nightly builds and integration testing pt 2
-
- Closed
-
1.
|
move ui test to the folio-testing-platform |
|
Closed | Matt Jones |
2.
|
Refine support for --workingDirectory with --run |
|
Closed | Matt Jones |
3.
|
Identify cause for platform-core failures |
|
Closed | Matt Jones |
4.
|
Update ui-testing |
|
Closed | Unassigned |