Automation is everywhere. Automation experts are in high demand. Nah! Not in high demand, ONLY Automation Engineers are in demand. All job descriptions mention a set of automation tools and frameworks. Interviews revolve around Java, Python, C#, Selenium, UFT, Appium, Frameworks, Algorithms, and what not. Literally ‘Everybody’ is looking for an Automation engineer.
Testing Fundamentals
No idea about Software Testing Basics? Get an Idea before your next Interview!
I agree situational interviews are the way-to-go, but some theoretical clarifications won’t do any harm. Every tester needs to know the basics at least. It’s essential to be prepared for a time-boxed interview. Get some basic facts clear before facing the next interview, to avoid embarrassment.
Database Testing | How do you get a Database Connection?
“How do you connect to a Database?” the interviewer asked. That was simple, right. Using a Database connection string I said. But what do you pass in connection string and how does it works at the backend? Oh Oh! They need the details. As a tester, most of the testing is centered on web applications (i.e. browser) and now-a-days mobile apps. But as with API testing, Database testing & SQL is growing in demand. Database knowledge is something every tester is expected to know about. So with this article we try to explain how to connect to a database, in detail.
I am Confused | How to write Test Conditions + Test Scenarios + Test cases
Testing terminologies can sometimes confuse even the most experienced of IT professionals. If you were asked to write a test case, you would know what to do. What about a Test scenario? Or a Test condition? The first step is learning what different Testing terminologies actually mean. To a layman Test conditions, Test Scenarios, Test cases and Test suite might seem similar but there is a subtle difference between these terms which make a world of difference for a Software tester. Each of these implies a different level of detail and is used for a different purpose. Once a tester knows what each of these terms mean, they can figure out how to use them to describe the testing work that is done on a daily basis.
Exploratory Testing is NOT Ad-hoc | It’s like Machine Learning
Exploratory testing, is all about discovery, investigation and learning. It’s like Machine learning, in concept. It empathizes on learning and adaptability. While the software is being tested, the tester learns things that together with experience and creativity generates new good tests to run. It emphasizes on personal freedom and responsibility of the individual tester. Exploratory testing is done without any specific plans and schedules. Test cases are not created in advance but testers check system on the fly. They may note down ideas about what to test before test execution. The focus of exploratory testing is more on testing as a “thinking” activity.
Testing != Bugs | The real purpose of Software Testing
Purpose, noun, the reason for which something is done. Recently a discussion was started by one of the Testing co-blogger at LinkedIn “What drives Quality Assurance? What is the purpose of Software Testing?” A relevant discussion indeed. They say “If you’re not working with purpose, you’re doing it wrong.” This triggered me to put on the thinking hat and pen down my perspective of ‘Software Testing Goals’.
Verification vs. Validation OR “Verification and Validation” in Software Testing
In software project management, software testing, and software engineering, Verification & Validation (V&V) is the process of checking that a software system meets specifications and that it fulfills its intended purpose. In the context of testing, “Verification and Validation” are very widely and commonly used terms. Most of the times, we consider the terms same, but actually the terms are quite different. In this article we will first explore Verification vs. Validation and then move on to its practical application in Software Testing.
Test Data Management | Test Data & its importance in Software Testing
Better Test Data management means faster delivery of applications, and ultimately, faster achievement of business objectives. Companies that fail to invest in Test Data management put themselves at risk of falling behind.
What is Waterfall methodology? The past of Agile!
Waterfall Methodology for Software development, introduced in 1970 by Winston Royce, is the pioneer of the SDLC processes. In fact it was the first model which was widely used in the software industry. Despite many new models being introduced, the Waterfall methodology is still the dominant process model. Additionally it is important to learn the know-how of Waterfall model in order to fully understand the emergence of Agile development methodology.
Software Testing Levels | 5 Stages to deliver a Quality Software
Software Testing Levels are the different stages that enable QA team to deliver a Quality Software; Unit > Component > Integration > System > Acceptance!
What is the Test Environment in software testing? | Test Environment Management
Test Environment is nothing but a replica of actual production environment (being used by end-users) with close-enough hardware and software configurations, where the testing would happen for the developed application.
The Karan-Arjun of Software Testing – cont…
Continuing on our tryst with Bollywood’s Karan-Arjun, let’s read about some more important duos in the field of Software Testing!
The Karan-Arjun of Software Testing – I
Similar to Bollywood’s Karan-Arjun Shahrukh Khan and Salman Khan, in Software Testing too we have multiple important duos. Let’s have a look.
Vande Mataram | What it means for Testing team
Independence & Freedom – everybody likes it. Wants it. Fights for it. And finally celebrates it. It gives you the objectivity to express your views & opinions. It is essential for a thriving society where the mind is without fear & the head is held high. As India celebrates its ‘Independence Day’ on August 15th, let’s see what it means for a Test team.