Data-cy IDs are gone for components (I assume due to the UI redesign)
For now I have created a new command to search and add a component. Tests have been updated to reflect this
Updated the current createScreen test file:
- Reworked a test related to access levels
- Tests for screens of all access levels and deleting all screens (and starting new screen journey)
- Added commands to delete screen and delete all screens
This test spec file fires off against every PR. There is some timing issues currently.
I am making a few changes in relation to timeout values (a small restructure too) in hopes this helps with the PR builds.
Tests pass locally for me, so there may be more changes required against this spec file as I check its performance
Getting close.... but there are still some minor timing issues against the smoke build.
I am increasing a few timeout values within postgreSQL & commands files
All tests pass locally, just having issues with timing on the CI run
Also reduced test retries (runs a total of 2 times instead of 3, the 3rd run does not add any value)
Account portal tests
- Visibility when accessing the portal with different permissions
Commands
- New command to logout when app grid is not present
- Need matching data-cy commands for this
Created a new folder called adminAndManagement
- contains user and portal based tests
Timeouts refactoring
- Replacing a large number of waits with timeouts - this will prevent less time waiting during all testing
New user test
- Edits user details (for now just adds first name and last name)
Commands updated
- Removing some waits and replacing with timeouts associated with 'get' Cypress functionality
We do not need to test templates this way via the UI
- There is currently a test which creates an app via a template
- These specific templates tests are time consuming and repetitive
- These template tests will be replaced by API testing
Commands.js
- Removing a publishApp function -> There was two, one is not needed
New Lead Generation Form template test
- Verifies app creation
- Successful Publish
- Published app opens when button clicked
Refactor of template functionality specific tests
- Created a command to publish app and either click view or done button afterwards
- Refactored into some template tests
Adding a timeout associated with the fetch tables request
Another attempt at sorting this for the smoke build - it only fails there and is timing related.
Changing structure for `addDatasourceConfig`
- Intercepting the request that is made when fetching tables from a datasource
- There is a specific issue with this in regards to the smoke build. This will allow me to see deeper into the potential timing issues that are occurring
createUserAndRoles.spec.js
- Timing issues with the test regarding the smoke build.
- Adding timeout values and reloading the page after role assignment
commands
- Adding a `clear()` to `createAppFromScratch` function.
- Previous test runs show that the placeholder value is being taken at times
Two tests for IT Ticketing System template
- Create and publish app
- Filter tickets by status (Skipped for now as functionality seems broken specifically for the CI run, looking into it...)
Commands
- Added new template navigation function
- Added this to appropriate template test files
Specifically the test for adding a URL param binding
- Issues with this test on against the CI (Works fine locally)
- Skipping for now while i investigate this further. Looks like some kind of timing issue for getting the url after a component has been added
Sometimes after adding a component, the incorrect component ID is selected, causing test fails. This wait should allow the correct component ID to be selected
commands.js
- Increasing wait due to timing issue for specific test runs.
- Added `{ force: true }` to assist with adding components
createApp.spec.js
- Increasing wait due to timing issue for specific test runs
Mitch-Budibase
Andrew Kingston
Dean