The test 'Should reflect an application that has been unpublished' failed on last nights build. This is likely a timing issue.
I have included a wait and timeout within the test. It passes locally, just not on the nightly build
Few changes to assist with the nightly build
appPublishWorkflow
- Removing closeModal function calls (no longer needed)
createBinding
- Update to remove a component from some of the tests
- New command for this also
REST
- Skipping these tests -> there are only 2 and will be replaced via API
Commands
- Additional changes to support the nightly build
- mainly navigation based due to recent code changes to the product
There are 4 tests in this file
- Skipped create and delete screen tests (covered by API)
- Update URL test remains (will eventually be covered via E2E with QA Wolf)
- Create and filter screens by access level test remains (This is due for API coverage within another ticket)
The + symbol button for creating an automation has been removed. It has been replaced with a button which says 'Add automation'
I have updated the create automation test to now click on this button when creating a new automation. This test was failing due to the other button no longer existing
The files are:
- addMultiOptionDatatype
- addRadioButtons
These tests are flakey from time to time and we no longer need them to be run consistently through Cypress. We will have E2E coverage via QAWolf and will also have some coverage via API Automation
Some of the tests in here are flakey from time to time.
- We had a failure on the nightly due to a flakey test within this file
- Skipping the tests in here for now (we will receive coverage via QA Wolf)
As previously discussed with Marty, any further flakey tests (timing issues) with Cypress will be skipped for now but not removed.
- Timing issues are effecting Auto Screens UI & PostgreSql tests
- We will receive coverage of these tests via QA Wolf
- The tests are not removed so we still have reference for generating relative API tests
A few changes to maintain what we have for the nightly smoke build
autoScreensUI
- Adding a 1 second wait. This seems essential now for the smoke run on CI. Was difficult to reduce the error locally but definitely timing related
userManagement
- Reworking how we confirm a user has no applications
- The text has also changed - updated it too
Skipping tests for Oracle & datasourceWizard
Both are covered during general regressions
There are timing issues associated with the CI Smoke run
This will help reduce the smoke build run time
The oracle test file was only covering a basic check of invalid configuration (Not essential for the smoke run)
rest.spec.js
- Test was flakey on last nights smoke run
- Updated to specifically search for query-buttons and then add query
commands.js
- Increasing timeout values for createTable & createDatasourceScreen commands
createComponents
- Updated how the test gets nav-items from the side nav bar
commands
- Updating maximum timeout value for cy.visit instances (this seems specific to the CI runs)
- Updated createUser command to ensure better timing between the create user modals
Update createTable test command
createTable command
- Changing how a check is completed when dealing with the create table modals
appPublishWorkflow
- Increasing timeout value related to the app table status
- This increased timeout value is needed specifically for CI runs
MySQL
- Timing issue for the smoke build
- Including an intercept after saving a query and then confirming it exists. Sometimes Cypress tries to find the query within the nav item section before the query has finished
PostgreSQL
- Timing issue for the smoke build
- Sometimes Cypress will continue the test before the page has finished reloading. Increased timeout value here to ensure the page loads. Also ensuring the entire nav item section is visible
In some cases Cypress is running too fast, meaning that the test runs ahead of what is actual seen on Budibase.
This issue mainly occurs at the start of the smoke build and around logging in.
I am attempting to combat this by ensuring the url includes 'apps' after logging in
We don't need a specific test file for this.
The test file will remain for now but will not run. The test will be reworked into a different test file or as part of the API testing
Some test changes for test files within the adminAndManagement folder
- Changes related to UI
- Restructured accountPortals tests
- Changes related to changing passwords (flow is different now)
Mitch-Budibase
Mitch-Budibase
Pedro Silva
Martin McKeaveney
Martin McKeaveney
Andrew Kingston
mike12345567
deanhannigan