We have a wdio-based automation project that does end-to-end functional testing. We use CircleCI as the CI/CD tool to run automation regression. When setting up a project with CircleCI, we need to enter all configuration details in the config.yml file under the .circleci folder. Earlier, we only had staging regression and prod regression jobs and their respective workflows in the config.yml file. As mentioned in this article, we also started doing screenshot testing for our application. With time, our configuration file expanded and became cluttered, accommodating various workflows like staging sanity, staging regression, prod regression, performance score

It is always a good practice to keep a check of your code quality and code coverage. Writing test cases for your code is extremely important as that helps you identify any failure before hand. There are many articles about how to write test-case and why we should write etc. However, I would be covering here, how we can integrate Test coverage to Code-climate in your Ember.js app while you are using CircleCI. In todays world most of us use auto-deployment (e.g. tools like CircleCi, Travis CI, Jenkins, Bamboo, Codeship etc.). We would like to get all the

Sometimes tests can be hard to debug, especially when they’re running on a remote machine.This can be done with ssh enabled build with CircleCi using Debug via SSH option. SSH can be enabled for already running build or with rebuild option. To enable SSH access for a running build, go to the ‘Debug via SSH’ tab and click the ‘Enable SSH for this build’ button. To start a fresh build with SSH enabled, for example if you want to debug a build that has already finished, click the ‘with ssh’ button alongside ‘Rebuild’: It provides key such as

Recently, in one of our in-house app, we faced issues with RSolr that failed all our builds in CircleCI. We faced following RSolr specific errors in our CircleCI builds for the repo. RSolr::Error::Http: RSolr::Error::Http - 500 Internal Server Error Error: Severe errors in solr configuration. Check your solr log files for more detailed information on what may be wrong. If you want solr to continue after configuration errors, change it to following configuration instead of null <abortOnConfigurationError>false</abortOnConfigurationError> After troubleshooting and debugging, we noticed that our repo in git just had