Black box testing, behavioral testing, or functional testing is a type of test that assesses the functionality of the application. While internal knowledge of the application is not required in this test, knowing the end-user requirements and specifications are critical as the main objective of testing is to verify the functionality is behaving exactly as expected.
When testing the application, the tester uses valid and invalid inputs and the output is verified against the expected. The aim of black-box testing is to find incorrect or missing functionality, errors in the interface, data structure errors, database access errors, and behavioral or performance errors.
While running a black box test on a CloudBolt appliance varies between customer’s environments, the idea of black-box testing in CloudBolt is to test the most critical capabilities of the software. This includes JobeEngine, accessing a server via console/RDP or ssh from CloudBolt, getting correct data from Reports, ability to sync brownfields servers in CloudBolt, API and etc.
Re-run all the Continuous Infrastructure Testing (CIT) tests after upgrading. CIT is an essential capability of CloudBolt Software that helps CloudBolt admins track down the test coverage of their infrastructure.
If you haven’t already configured CIT in your CloudBolt appliance, configure it before upgrading.
Once you have verified the tests are completed successfully without any environmental issues, re-running those tests after the upgrade saves a huge amount of time. See the CIT page in the docs for more information.
Re-run sync VM jobs from Admin > Recurring Jobs. This option helps verify the status of a job engine and verifies that servers are getting updated with the correct status as they are in the resource technology.
If you already have automation in place to make a call to CloudBolt API endpoints, re-run the test. Otherwise, make a simple call to any CloudBolt API endpoints listed at https://your_CloudBolt_server//api/v2/. See CloudBolt API documentation for more information.
Recurring jobs at Admin > Recurring jobs is a good place to automate a test against Reports. In case no automation is available, manually running a report from Admin >Reports can verify the status of a report and the generated reports.
Try to access console/RDP/ssh to a server that you have been working on prior to the upgrade.