Skip to content

CDB Test Plan

Jump to bottom
Dariusz Jarosz edited this page Jan 26, 2023 · 4 revisions

Purpose

Define tests that need to be done before any a new version of CDB can be released for production environment.

Environment

To perform the pre-release tests, the CDB must be deployed on a local environment. This includes the payara server (it can run through netbeans but is not required). A local mysql database that is configured for the deployment. The command in the execution section will take a snapshot of the database and restore an appropriate test data for the tests.

To setup a local environment. please refer to instructions in the CDB Readme

Execution

The following command will start the execution of all the tests defined below as well as populate the database with appropriate test data.

cd $CDB_DIST_DIRECTORY
make test

Overview of Tests.

The releasing of CDB consists of multiple tests that include maven build & test.

Maven Build and tests

  • Ensures a successful build of CDB.
  • Includes a few unit tests for the following modules:
    • CrpytUtility
    • StringUtility

API Tests

Before the test is executed a new API client is generated using openAPI spec file that CDB generates. This ensures that the latest version of API will still work as expected.

The following tests are executed during the API Test.

  • Update location parent as admin
  • Update location parent as user
  • Fetching item
  • Update contained item
  • Get items derived from item
  • Item permissions
  • Item status
  • Update location
  • Create and delete location
  • Update item details
  • Update item property
  • Add log entry
  • Upload document
  • Upload image
  • Fetch item by domain
  • Search
  • Test cable api
  • Test domain api
  • Test log api
  • Test machine api
  • Md update assigned item
  • Md create placeholder
  • Md move machine
  • Md control api
  • Create promoted machine element
  • Update representing assembly element for machine
  • User route
  • Fetch concise item list
  • Create catalog item
  • Create catalog element
  • Create inventory item
  • Add allowed property value
  • Search
  • Get control herarchy for machine
  • Get machine connection list
  • Get inventory located here
  • Get cable design connections

Selenium Test

The script relies on chrome to perform the Selenium tests. Before the tests begin the make test attempts to download appropriate chromedriver to match with installed chrome browser on the system.

The following tests are executed during selenium test run:

  • Create property type
  • Create catalog item
  • Machine design
  • Machine design export
  • Machine design import
  • Machine design details page
  • Machine pages
  • Browse by function pages
  • Browse by owner
  • Browse by location
  • Catalog pages
  • Catalog export
  • Catalog import
  • Cable catalog pages
  • Cable catalog detail page
  • Cable catalog export
  • Cable catalog import
  • Inventory pages
  • Inventory detail page
  • Inventory import
  • Cable inventory pages
  • Cable inventory detail page
  • Cable inventory import
  • Cable design pages
  • Cable design detail page
  • Cable design export
  • Cable design import
  • Source pages
  • Source export
  • Source import pages
  • User info pages
  • User info export
  • Connector type pages
  • Connector type export
  • Location pages
Clone this wiki locally