• tcw v2.04
• Introduction
  • Overview
  • Lab Flow Diagram
  • Architecture Diagram
  • Credentials Quick Reference
• Act I - Build
  • The App
  • Add some data to Production
  • Updating the Data Repository
  • Some Automation Details (part 1)
  • Viewing the Data Repository
  • Let’s Make Some Changes
  • We're Building!
  • Not So Fast!
  • Fix Our Script
  • We're Building! (Again)
  • Validate Our Build
• Act II - Test
  • Works in My Environment!
  • Automated Testing
  • Some Automation Details (part 2)
  • Oh Snap! A bug!
  • Ready to Test Again
  • Bugs Happen
  • Triaging the Bug
  • Squash the Bug
  • Deploy to Production

Our Job completed, but the build is unstable (orange with an !). It appears that our tests have failed in the Automated Testing phase.

In this scene, we will first take a look at the test artifacts in Jenkins to ascertain what happened. Next, we will login to Bugzilla and validate the bug report against what we see in QA. Finally, we will look at the corresponding bookmark on our Test data pod in the Delphix DDP.

YOUR STEPS FOR THIS SCENE:

1. Activate the Jenkins tab
2. Click on the Tests button (in purple rectangle below)

   

   
   

3. We can see from this screen that the Add Duplicate User test failed (a duplicate user was allowed)

   

   
   

4. The test failure created a bug. Let’s check that out.
5. Activate the Bugzilla tab.
6. Click Browse

   

   
   

7. Click TestComponent

   

   
   

8. Click on the most recent job. It is #3 in the example below.

   

   
   

9. Scrolling to the bottom of the bug, we can see the test results and reported failure.

   

   
   

10. Let’s reconcile what we see in the bug report and test results against the QA environment. Click the Patients QA bookmark.
11. Log in to the QA instance of the Patients application using credentials

    

    
    

12. If you logged in successfully, you should see a list of patients in your browser

    

    
    

13. The test report indicated that it failed because it was able to add a duplicate user. Click the Users button (purple rectangle below)
14. Ack! We do have to users with the same username mcred. This could cause significant issues as our product rollout expands.

    

    
    

15. Activate the Dynamic Data Platform tab.
16. Login as qa, if your login has timed out.

    

    
    

17. Click on Test

    

    
    

18. Click on the most recent bookmark icon. Does it match the job number from Jenkins? Does the bug tag on the bookmark match the defect in bugzilla?

    

    
    

19. The bookmark has been shared back with the developer. Let’s make the dev clean up their own mess.