Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Testing in DevOps


Hello All, 


I am quiet new to DevOps and I am little confused about testing (automated) in devops... I mean, while setting up a simple pipeline, I wanted to know what are all the test to be executed and also where exactly in pipeline these tests to be executed.

Consider a simple java based web application as an example....

Please give me some insights.... 


Below is a brief summary of pipeline of this project based on my level of understanding of devops... 


A code is in github and when a change is committed to the repo, a new build is triggered and I believe during the build, code will be reviewed, compiled and also a unit test will be executed to thus compiled code(pls do correct me if I am wrong here) and then the code will be packaged and deployed to a test environment. Please guide me. 





1 answer

1 accepted

2 votes
Answer accepted

Hello @chandag !

Yes, you're getting the gist.  Once a commit happens, unit testing should happen automatically.  Other checks such as listing could occur at this stage.  If the tests pass, the commit is allowed.

You can also automate the merge of changes back to a higher-level branch (including master/main).  More tests including some BDD-style tests can be run.  Once merged, automation can create the deploy packages and deploy to staging or even to production.

Use of this CI/CD pipeline is one of the fundamental practices of DevOps. 

Hope this helps.

Hello @Robert Wen_ReleaseTEAM_ ,

Really appreciate your reply. Just got a quick follow up question.

Could you please let me know if all the tests be conducted only after a build has been deployed to a test server or are there any tests that can be or should be done directly to a build (.jar/.war file) before it has been deployed to a Test server.

It depends on the type of test.

SAST (Static Analysis) scan the source code to find errors and security vulnerabilities.

Dependency scans are done either before or after a build.  They scan libraries to see if security vulnerabilities exist.

Dynamic Scan (DAST) are run against a build on a test server.  BDD tests are also run against a build on a test server/production server

Like Steffen Opel _Utoolity_ likes this

Thanks @Robert Wen_ReleaseTEAM_ 

Actually what I thought is when a test is conducted just on a build (.jar/.war package), it is not possible to conduct any functionality test. Am I right here?

So, If I am right, then BDD testing doesn't test any functionality? (assuming we are talking about a web application).

Also Does Integration Testing happens against build? or Does it happens against application? Same question for Regression Testing...

Also should the tests on a Build should happen only in Test server/Prod server or can the test be done on a build in Jenkins Server itself?

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events