Tests hold a prominent status in the framework, with serving as the internal testing framework. Writing test cases is made effortless due to the framework's preconfigured support and settings. Ember JS Qunit However, challenges may arise, particularly when certain errors surface exclusively in the continuous integration (CI) environment and not during local development. These errors can stem from configuration issues or discrepancies in the written test cases. In this article, I'll share a specific incident where an error manifested solely in the and how it was identified in the Jenkins logs after some adjustments. CI environment My CI setup utilizes Jenkins, with pipelines designed to execute test jobs. Unexpectedly, the tests were failing and leading to timeouts. Before delving into the timeout error, it's essential to shed light on , a JavaScript test runner responsible for executing tests in web browsers. Testem While Testem successfully launched the browsers in headless mode, it encountered issues loading the test cases. Some of these errors were captured in the Jenkins default console log, but they didn't provide the necessary insights. To find a solution, I scoured the repository for similar issues. Although I gained a better understanding of the problem, a definitive solution remained elusive. Testem Github Subsequently, I discovered that it was possible to log Testem-related information in a dedicated logger file, as detailed in the . This discovery opened up a new avenue for resolving the issue. Ember CLI documentation To log Testem-related logs, we need to use ember test --testem-debug <FILE-NAME> I could easily access those logs during local testing and was thrilled to have them available in the CI environment. However, I encountered an issue: these files were absent from the Jenkins workspace. It appears that to retain files for later analysis, we must make use of . To archive a file in a Jenkins pipeline using the strategy, you can simply employ the following syntax at the conclusion of the stages: Jenkins Artifacts Stages post {
      always {
         archiveArtifacts artifacts: 'testem.log'
      }
    } Or if you use it directly inside a node, something like below (which was in my case): node('node-name'){
 try{
   .....
 }catch {
   ....
 }finally {
   archiveArtifacts artifacts: 'testem.log'
 }
} Once the artifacts were configured, I successfully accessed those logs in Jenkins CI. Thanks to the log information, I managed to identify the root cause: the host application couldn't establish a connection because I was utilizing a custom hostname. To address this issue, I needed to include these hosts in the pipeline script's list of allowed connections. sudo -- sh -c "echo 127.0.0.1 localhost.demo.com >> /etc/hosts" With this modification, the errors disappeared, and I regained the ability to run tests smoothly in the Jenkins CI environment.

Walkthroughs, tutorials, guides, and tips. This story will teach you how to do something new or how to do something better.

Troubleshooting CI Test Failures in Ember JS with Jenkins: A Journey of Discoveries

About Author

Comments

TOPICS

THIS ARTICLE WAS FEATURED IN

Related Stories

104 Stories To Learn About Continuous Integration

139 Stories To Learn About Cicd

Our Ancestors Could Have Solved Food Scarcity With AI - Noonies Nominee TRex

15 of the Best Continuous Delivery Tools

Improving the Working Environment for Developers - In 3 Stages Only

5 Best Microservices CI/CD Tools You Need to Check Out

104 Stories To Learn About Continuous Integration

139 Stories To Learn About Cicd

Our Ancestors Could Have Solved Food Scarcity With AI - Noonies Nominee TRex

15 of the Best Continuous Delivery Tools

Improving the Working Environment for Developers - In 3 Stages Only

5 Best Microservices CI/CD Tools You Need to Check Out

Light-Mode

Classic

Newspaper

Minty

Dark-Mode

Neon Noir

Minty

HN StartUps