As a software examiner, how do you adapt when a new technology or process is introduced within your team? Do you panic? Do you accept it as a challenge? Do you research to find a solution along with the team? Do you reach out to citizenry in the community to see how they approached it? Or do you exactly expect it to magically work for you without any effort on your part?

I was in similar situation when our team decided to adopt Continuous Integration (CI), as we were transitioning & nbsp; to a DevOps culture. I would care to percentage my experience of how, as a quizzer, it was to go through the journeying.
 

It & nbsp; had been a while since we started to act in agile from waterfall. We took child steps and evolved slowly. We were all happy, comfy, and settled into the way we be approach agile & nbsp; with & nbsp; our scrum procedure. Just when we were felicitous that we went through the agile transition from waterfall, now it was a new challenge of transitioning to DevOps. We had to embrace another new change of process, and it was the introduction to the world of pipelines - it was the CI/CD world!
 

As a tester you always like challenges, and this was challenging because I had to understand a new way of how testing convulsion in uninterrupted integration, and bosom the new eccentric of value it could provide while working on it.

As a tester I was very rummy to know: & nbsp;

• What it brings to my world of testing

• How would it affect current test & nbsp; summons

• What do I have to change

• What welfare do the pipeline get?

• What do they look like?

• How do they work?

And on and on. It was pretty confusing and shuddery at the beginning to visualize the change.

For autonomous testing across multiple user personas, check out SUSATest — it explores your app like 10 different real users.

Why is our initiative instant emotion towards any change ‘ Scary ’? Why ca n't it be an excited feeling or enthusiastic feeling for trying something new - I ask myself this question. Then I thought to myself, it 's as simple as & nbsp; this - When you do n't know about something, you are always scared & nbsp; about the change, but if you find safe and see it as a new challenge, you will definitely get excited.

Then I started to explore and read more about line. It was n't surprising that the more I was reading, the more I was confused. Then I settle to draw those pipelines and visualize them.

I sat with my colleagues and said: `` Let 's please visualize the pipeline by drawing it on a big white plank. '' They & nbsp; agreed and we had a whole discussion around these pipelines. And we finally agreed on this and it looked something like this initially:
 

That ’ s where it started to make more sense to me, and I got a best understanding about what just this uninterrupted integration is - but all in theory though. What I understood at this point was that it is simply nothing but a step by stride process to unloose the code once there ’ s a commit.Continuous Integrationis a pattern for integrating the codification several times & nbsp; to receive a quick feedback without expect long. Whenever the developer finishes maturation task and pushes the changes to the secretary, that ’ s where the grapevine stage starts. Because it has degree, it is called as a grapevine I thought to myself. & nbsp;

Now, a few more questions came to my mind:

• What are those stages?

• Who define those stages?

• Who define what should go in the line and when?

• Will I have any spot as a quizzer to suggest something?

• The big question was - will there be no manual testing at all?

We as a team had discussions and come up with the our own version of the pipeline because there ’ s no classic structure for a Continuous Integration (CI) pipeline. We decided we shall run unchanging codification analysis, unit tests and integration tests as our initial stages of our grapevine. This stage would create a unique artifact which could be deployed on a tryout environment to run additional trial. As my savvy got best about pipeline, I started to suggest that we add more valuable exam to the pipeline.

Initially we added smoke tests to the pipeline which would run alongside the existing tests. The reason why I propose to add smoke tests as part of the pipeline was to get sure the build is testable before it is deploy on a test environment for further examination. I just called it as fume test, but we could call it a Build Verification Test or Build Acceptance Test too. If the test & nbsp; did n't legislate, the build would be rejected and a new frame would be released once the failed trial were fixed.

I could see each stage of tests running one after the other. It would kibosh going further if there was a failure & nbsp; at any of the tests or stages. Is n't that magic!!!

It was but the beginning for us and especially for me. I continued to understand and discover more and more, and then I discussed with my squad if we could add fixation screen to the continuous consolidation pipeline. But initially we did not wanted to add any long running tests to the grapevine as we thought the unscathed point of having these grapevine & nbsp; was for quick feedback. So we resolve to run the regression tests as nightly run task instead of run it with every commit. But we had the goal to run these regression test with every commit once our grapevine was matured plenty, when we would & nbsp; decide & nbsp; to run those tests in latitude. But that was a long condition goal.

Each dawn I could see the results of which examination where passed and which were failed and the dispute was that I & nbsp; could add the build number while raise the matter, so it & nbsp; got easier for a developer to encounter the origin cause. It 's not to say that it tells you where exactly where the matter is but they could easily check the recent codification related to that build to see what went wrong. Instead of searching a needle in a haystack, it 's like you cognise which part of haystack you need to look to regain the needle.

 
I got to spent most of my time as tester & nbsp; defining & nbsp; the test strategy, explorative examination, being part of the 3 amigos to refine user floor and acceptance criteria, ascertain the test feedback from the line, and adding more worthful tests to regression tests.

As we got on and had more pellucidity and saw the benefits for having these pipelines in place, we decided to discuss a long term goal, where I advise to have visual examination & nbsp; as part of the pipeline as good, from a try point of survey.


This was & nbsp; my actual line journeying into the creation of testing! It was very challenging and interesting!!

Thanks for reading my level!! & nbsp; Happy Testing!!!!