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

Running pytest in pipeline with kubernetes


When I run unit tests (written in pytest) in a docker container in the pipeline I get the result straight to the pipeline GUI (I.e. if one of the tests fail the step fails as well)


I also have e2e tests written in pytest with a specific step in the pipeline for each. 

Those tests are triggered via a KUBECTL_COMMAND instead of a docker command.


The problem:

The pipeline GUI shows that the step has succeeded with no context to the success of the tests, but to the success of the kubectl command instead, which essentially only indicates that the pod/s were successfully run by the pipe (atlassian/aws-eks-kubectl-run:1.4.2).

I can watch and monitor the tests results from the pods via another 3rd party application the pod is reporting to directly, but this doesn't come close to the clarity and convenience the bitbucket pipelines GUI offers when it comes to Unit testing in a container. 

How can change the pipeline behavior so it understands that initializing the pods isn't the success measurement of the step but the tests (pytest) inside them? 

1 answer

0 votes

@david  Hi. Thanks for your question. Please provide us with details about your case: pipeline configuration, logs etc.

Regards, Igor.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events