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
Skipping test that attempts to add datasource without config
-Eventually times out with empty error message.
I will raise a bug for this. Skipping the test to keep the automation running
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
The tests are
- Filter application by stage
- Edit application
The template functionality seems to differ between test env, CI, etc. Skipping these tests for now while i debug, and leaving the passing tests in
Edit an application
- Change application from not hired to hired
- Confirm relative sections update
Delete an application
- Currently skipped as there seems to be an issue with deleting an application within the template
2 more tests associated with the Job Application Tracker template
- Add active/inactive vacancies
- Filter applications by stage
Tests utilise pre-populated data already associated with the template
jobApplicationTracker.spec.js
- New file and test
- Creates and publishes Job Application Tracker app. Also verifies View URL button works
commands.js
- Updated deleteApp function
Added tests which check the details button for each template.
- Split per category (Will add more specific template tests under each category)
- Checks template name matches url (There are a few exceptions)
- Checks status of url - expects 200 back each time
Also updated the DeleteApp Function
- Fixed a smoke test issue associated with deleting the tests app
Datasource (MySQL, PostgreSQL)
- Test should now pass for smoke build
Table Tests
- Removed pagination tests - no pagination in the smoke build test run
PostgreSQL
- Test fixes (May still fail due to connection issues on smoke build)
Oracle
- Test fixes
- Skipping most tests (Oracle host needs configured)
commands.spec.js
- minor change to addDatasourceConfig function
renameAnApplication - changing the navigation to a direct URL rather than clicking the home logo button
createUserAndRoles - Removing the After action (now supports correct flow of tests)
Passes locally but looks like a timing issue when run against the CI.
Adding and increasing wait times to hopefully combat this. I will extend further if unsuccessful
I've made some changes to the tests and commands file to allow for the tests to run within the Test env after the latest round of UI changes.
Some of these changes also allow for testing instances in which apps already exist - This is specific for the test env, the CI runs always have a clean instance
Dean
Mitch-Budibase
Rory Powell
MihailHadzhiev2022
Mitch-Budibase
mike12345567
Mihail Hadzhiev
Martin McKeaveney
Peter Clement