I have a few tests that pass on my machine, but fail in Travis CI. Is there an easy way to debug those tests? My project is in Ruby.
Related
I needed to setup a Jenkins pipeline and I wanted to know if unit test should run before the actual compilation of the project
The Jenkins pipeline currently runs unit and Integration test before the bundling and wanted know if that's ok
When a new feature of a microservice is merged into development branch, is it always deployed to Kubernetes test environment.
If yes, what happens if e2e tests fail? Is the microservice deployment rolled back?
Is automated rollback common in CICD in the industry right now?
Is there any other way to make e2e blackbox tests without deploying to Kubernetes test environment?
I could not find a good example about that?
When a new feature of a microservice is merged into development
branch, is it always deployed to Kubernetes test environment.
Yes, you are right
If yes, what happens if e2e tests fail? Is the microservice deployment
rolled back?
Since it's a development environment ideally it should be fine to run the broken version however more depends on the requirements or architecture you are planning to follow.
Is automated rollback common in CICD in the industry right now?
Yes, that's common however it would be better to keep it as Manual action, you might have a scenario where you want to deploy the version while e2e failing.
The benefit of Manual action as require might get change and have to deploy feature in which integration testing failing or something else.
Is there any other way to make e2e blackbox tests without deploying to
Kubernetes test environment?
You can do the subsystem or small portion testing in CI/CD, e2e also you can automate on CI/CD side and integrate the Kubernetes service accessible to the CI server for testing.
I wanna study Travis Ci with flutter, but normally it is used for testing. But, I have no time to run how to test applications and only want to use it for the build.
Is it useless for only building goals or worthy?
I have a jenkins CI setup configured to run specs on each git push. When I run these specs with "rspec" on my local it works fine with zero failures, also I ran specs on the CLI of jenkins agent the specs ran with zero failures. But when the same specs run in jenkins CI, some cases fail.
I have been trying to figure out the issue but have not found the real reason for this behavior yet.
Can anyone please help with this issue?
I have recorded some simple selenium tests by Selenium IDE. Now I want to run those tests in Jenkins.
Which plugin to Jenkins do I need to do that? And how to run the tests step by step?
My test suite is in HTML.
Can you provide detailed steps for it?
Why isn't enough to run the selenium tests from maven though jenkins? This is how we made it work. If your jenkins is running on unix environment you should bear in mind that additional configuration of the system are needed.