Any technology or tool is worthless unless it is being used by ‘some’ organization somewhere. It all starts from organizations adopting the new technology or a tool and then it gets popular slowly. In that sense QA Job Descriptions are a great source of current technology, i.e. practical tech. being used by IT organizations. Be it Selenium, Protractor, Appium, API tools, Big Data Testing, etc. Everything is embedded in the QA Job descriptions, you just need to mine some data 😉 But don’t worry. Software Testing Studio has started a new series for you – “JD Talks” where we mine hundreds of Job descriptions to come up with latest tools, technology, languages and concepts. Let’s see what the first set of JDs talk about…
In continuation to our previous article introducing ‘Maven Build Tool’, this article describes some of the most common terms encountered while using Maven. These terms, that have an explicit meaning for Maven, can sometimes be confusing for newcomers. As an Automation QA, you should at least be aware of the below 20+ Maven terminologies – commonly asked in a technical interview as well.
Maven. You must have heard or read about this tool in your automation journey. Moving from a beginner to an automation expert requires knowledge of Selenium Tools Galaxy – Webdriver, Log4j, Extent Reports, Apache POI, TestNG, Maven, Jenkins and Cucumber. These tools serve different purpose in the automation galaxy and are a must-know if you really want to excel in your career as a Test Architect. This article is to introduce the ‘Maven’ tool, which is a Yiddish word meaning “accumulator of knowledge”. But what is being accumulated here? The Selenium Automation project’s build components. Let’s kick-off with our Maven understanding…
Interview is the most important part of the employment process. It can make or break an opportunity. When it comes to Software Testing, almost all organizations are now looking for Automation engineers, SDETs, Selenium experts, Automation architects and what not. Since Manual testers are finding it tough to land a high-paying job switch, many have started learning the basics of Selenium automation (Yeah! Selenium is one of the most popular automation tool now-a-days). But interviewers demand practical experience. And interview questions reflect that view – starting from basic theoretical knowledge, slowly the interview will move towards – Explain Test Automation framework for your current project.
Agile, Continuous Integration and Continuous Delivery methodologies have evolved in favor of delivering the software faster. Software Test automation blends perfectly with these methodologies for accelerating the time to market. But achieving a flawless test automation is same as preparing a delicious dish where essential ingredients play a vital role in the success.
Recently I am observing a rise of API Testing in the Job descriptions. I once did Web Services testing using SOAP UI testing tool, i.e. verifying the XML request-response. Thought it would be a good time to refresh the concepts. Anyways it was on my list since I started STS. When we look at the Software Testing trends, API testing is rising in priority & relevance. Let’s deep dive into the world of API Testing…
Experts and Influencers from the Software Testing industry say that – Software Testing is one such process that has no end and it demands for improvement every now and then. Testing teams strive to deliver a well-tested software that can provide a seamless user experience in terms of functionality, performance and security. The ever-evolving scope of improvement in the Software Testing process to deliver a better-quality software compels to adopt new approaches. Manual Testers are finding it hard to stay relevant in today’s evolving technology landscape.
Selenium WebDriver makes direct calls to the browser using each browser’s native support for automation. It support multiple browsers, operating systems and programming languages. What’s more? It’s FREE, ‘Open Source’ as we call it! Why do you think it’s so popular? 😉 Though Selenium Webdriver is at the epicenter of automated software testing, it is supported by different tools to make Automation Testing easy, effective & efficient – The Automation Galaxy of Selenium Webdriver tools!
Software Testing is a process of verifying and validating an application against the specified requirements, mostly functional requirements. The non-functional aspects of an application such as performance are considered only after functional. Testing a software for both functionality and performance becomes a value addition to its quality before its launch into the market.
The goal of every IT organization is to deliver a quality software to their clientele, and to complement their goal they give the highest priority to Software Testing. Automation testing acts as an accelerator to their time to market by saving time and effort, and manual testing will remain as the core for quality software delivery. In today’s changing technology landscape, Manual testers are being pushed to learn automation skills. But how? How to empower Manual Testers to do Automation Testing?
In an agile business, automation is becoming an essential process. Companies are now taking advantage of automation testing tools to increase their efficiency and productivity. Automation is frequently evangelized as the cure-all of software quality woes. Some of the benefits that accrue from automated tests include test reusability, repeatability and coverage besides the savings on effort, time and cost it takes for execution (compared to manual testing). However it’s NOT the answer for everything. Test automation, while being able to improve numerous aspects of software development, has limitations that developers and quality assurance teams should be aware of from the start. Understanding these limitations of automation testing will help us devise an efficient & effective automation strategy.
Load Multiplier is a highly scalable testing solution catering to needs of global customers in areas of Web, Custom protocols, HTTP, SIP, WebRTC, RTP, SRTP, JSON, XML, STUN / TURN / ICE and few more. It supports any text / binary based protocol testing. Additionally Load Multiplier can act as wrapper over any software and brings on large number of such instances to simulate a real field scenario.
Different browsers render applications differently, so web applications need to be able to detect on which browser they are running and adjust their app code accordingly. Successfully testing all browsers and all versions are no small feat which is exactly why Sauce Labs built their solution on Selenium. To enable QA teams to execute Selenium based automation suites on multiple permutations, operating systems, and versions, for multiple browsers and browser versions.
At first glance, this seems like we’re done and this is the perfect solution to achieve complete application matrix coverage. Unfortunately, nothing is that simple, and upon digging deeper, it is apparent that not all environments are available for certification. You will have some critical use case gaps, there’s no way around it. So what are they and how do you get around them?
“You cannot test iOS Apps without an iPhone or a MacBook” – are you one among the many who think so? Everything about Apple being proprietary, many of us tend to think so. But let me tell you – It’s partially true – You cannot skip the real-device testing altogether, but before reaching there you can surely perform a thorough App test using iPhone Emulator / Simulator (for Windows). Yeah! You read it right.