Shift left in Software Testing

-
We live in an era where technology is rapidly changing every day. Coming from the testing background having nearly 5 years of experience I have seen a lot of changes in the industry. We started from a waterfall model which transitioned to Agile methodology which further is moving to either DevOps and FSD/ SDET. It is the time where changes are also happening in the Automation industry, now the companies require resources who are well aware of API testing. So our organization has come up with an initiative to transform Agile resources into Full Stack developers. It surely will be a challenge and this is also known with the term Shift Left testing.

Shift Left in Software Testing

When testers are directly involved with the development team while building software or product, this process is called Shift left and it is now adopted by a lot of companies. A tester must have the knowledge of unit testing frameworks initially such as Spring Core, Java to begin with this initiative.
I believe it is a good initiative by the organization to adapt the market trend and train its resources for future challenges. The client has been demanding a lot of changes themselves to ensure smooth delivery of the software.

Shift Right in Software testing

Whereas few testers are involved in resolving the production defects along with the developers, such process is called as Shift Right and it is also implemented in the IT industry.

I hope above terminologies are clear to you. Happy Learning and happy sharing

Comments

Post a Comment

Popular posts from this blog

Azure Tutorials Series - Azure Networking

-
Image
In this article, we will learn about Azure networking concepts such as architecture, microservices, virtual networks, VPNs, subnet, VPN gateways and most importantly Network Security Group(NSG). All these terms are to be understood if you appearing for AZ900 Microsoft Azure Fundamentals exam. Azure Networking In previous articles we have learnt about Micro- services and how they work, these are alos loosely coupled architecture. Some of the features includes Independent components interact with each other with the help of queues Can be updated and deployed independently Highly scalable Supports Asynchronous messaging N-tier Architecture Supports loosely coupled architecture Application divided into multiple tiers such that higher tier can access lower tier but not vice versa Tiers are re-usable and can be updated or replaced easily without any hassle. Three-tier in general Web Tier(front end) Application tier(back end) Data tier(Storage) Virtual Network Isolated network shared by few g
Read more

Coforge Interview Questions | Automation Testing profile

-
Image
In this article we will cover recent Coforge Interview questions asked for testing profile.  Date of Interview - 19th December 2020 Mode of Interview - Web conference through TEAMS Interviewer - Rahul Sharma Round - L1 Coforge Interview Questions | Automation testing profile Round L1 Tell me about your project I have been working as a QA for XYZ company from 5.4 years, during this tenure,  I have learnt about Manual testing, Selenium, Database testing, TestNg, framework designing and API testing. What is a webdriver? A webdriver is a an automation framework that allows executing our tests in different browsers. It also supports headless execution using HtmlUnit driver. What are hooks? @Before and @After are called Hooks, they are used before and after any test scenario. How would you like your automation framework to be designed? How can you use data properties in Test NG framework? Explain Access specifiers? Access modifiers define the visibility of the class. There are four different
Read more

Testing in CI/CD

-
If you are part of testing fraternity you would have heard CI/CD numerous times by now. It's the talk of the software testing town. In this article, we will cover the basics of CI/CD, what actually it is and how it is implemented in software testing. What is continuous integration? In simple terms, development teams can integrate their code into a shared repository. This helps in maintaining code quality and identifying potential issues with the local version of the code at an early stage. What is continuous delivery? Everything that is being continuously merged by the development team, is continuously deployed to the live environment. Continuous delivery is often coined as ‘Continuous Deployment’ as well. Since most developers work in parallel, continuously integrating their code into one repository would mean that the master branch is continuously updated with new features. In order to ensure that there is no compromise in the code quality with so many changes
Read more