Manual test

3 minute read

Manual tests go through the functionalities of a software and interact with the software and the APIS. If you want to assess if the software conforms to the primary objectives, then manual tests help to verify a build when you introduce a new feature into the software.

Manual testing configuration

manualtest

Enter the following details:

  • Test Configuration Name*: Specify any name for your manual test configuration.

  • Test Results: Configure the manual test results.

    • Enter Manually: Enable the radio button to manually enter the test results.

    • Pull it from TCMS: Enable the radio button to pull it from TCMS.

  • Test Result Formats: Specify the test result format.

    • Test Result Format*: Select the test result format from the drop down.

  • Quality Gate: A quality gate is defined by DevOps teams to stop or fail a build by setting up a certain threshold value against whose detection, the build can be halted or continued. Specify any one of the following:

    • Yes: Enable the Yes radio button to allow pipeline to proceed even if the tests fail (at a specific tolerance level such as 90%).

      • Failure Tolerance: Define the failure tolerance such as 90%. If 90% of tests are successful and 10% failed, then the pipeline will still proceed.

    • No: Enable the No radio button to stop the pipeline from execution if even one of the tests fail.

Ability to override the quality gate

On test execution if your Tests are failed and the QualityGate threshold is met the Pipeline will be failed. Enable Ability to override the Quality Gate, If you want the pipeline to RUN even if the Quality gate threshold is met.

Schedule

  • Enable the check box for a test to run at a specific time when a commit happens. You can schedule in the following ways:

    • Force Start: Enable the force start if you need to run the pipeline before Schedule time.

    • Every: Enable the checkbox and select the time (in minutes or hours) to run a test.

    • Time: Enter a specific time. When a commit happens, the test step waits until the defined time and runs at the specified time.

    • Time Zone: Enter the time zone. The test runs at the defined time and in the specified time zone.

    • Recurrence: Enable the check box and define a weekly recurring interval for a test to run on a specific day of the week, when a commit happens.

Notification

  • Enable the check box to notify the user upon the completion of a test.

    • Success: Enable the check box to notify the user when a test is successful.

    • Failure: Enable the check box to notify the user when a test has failed.

    • Notify Committer: Enable the check box to notify the user who made the code change and committed. The platform automatically identifies the user who has committed the code change and notifies the committer.

    • Mode: Select the mode of notification

      • Email ID: Select the mail ID of any specific user from the drop down to send the notification.

      • Slack: When you want to get notification on the Slack tool, you can select Slack → Slack endpoint and Slack Channel.

      • Send Event to Observability Tool: You can also choose to send notifications on the Observability tool by selecting the Send event to Observability tool→ Tool name*.

All the fields marked in Asterisk (*) are mandatory.