Sometimes systems crush. And when they crush, they become headline news. The past few years have seen a sharp increase in the number and severity of software glitches at major companies. These newsworthy software “fails” have a negative impact on customer satisfaction & public reputation. The aftermath of each new failure is frequently projected across the internet, and can follow businesses around for years. The results of a phenomenally simple software error can affect the life of millions of people in the most negative way. Let’s take a look at some of the top Software glitches of 2017 to serve as a reminder of just how important Software testing is.

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. Continuing on our “JD Talks” series – we mine hundreds of QA Job descriptions to come up with latest tools, technology, languages and concepts. Let’s see what the second set of JDs talk about…

This article covers 10 of the most popular front-end technologies which everybody in the technology business should be aware of. So next time you go for an interview or join a new project – always tend to learn different technologies that build a product. Though QA is one of the part, but it makes all the sense to know about the complete product & technology that you are about to deliver. Quickly lets jump on to the top ten front-end technologies arranged chronologically.

Till now we have focused on numeric arrays. But they are most common. Everybody prepares that for the interview. In order to verify the OOPs concepts, interviewers are now asking about Java string programs instead. Why? Simple – because Java string programs are a bit level high than the simple arrays and it requires you to use different OOPs concepts like Java collections, arrays, String libraries, etc. Additionally, ‘String’ forms one of the important aspect of web applications as well as test data. This article will focus on five such Java String algorithms.

Different tools serve different purposes, the selection of tool should be done on the basis of your project requirements and application under test. Whatever tool you pick, it should empower you in achieving your automation testing goals.

The complexity of Software systems and the demand of customers and users are increasing every day. It has become evident that testing must be treated as a disciplined and controlled process. Test professionals must learn precise techniques and methods by which they can deliver software with a much higher degree of confidence. Individuals who are charged with the responsibility of testing computer systems must receive formal education, i.e. Testing Certifications. Testing certifications are in great demand! It is assumed that you already have one of them or at least you are planning/preparing to have one of them soon. Being a Software Tester, is it mandatory to have an ISTQB Certification?

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.

Writing automated tests is more than just a luxury for any agile software development team. It is a need, and is an essential tool to find bugs quickly during early phases of software development cycles. Although writing automated tests may seem like an easy task for engineers, there is still the possibility of ending up with poorly implemented tests, and the high cost of code maintenance in any agile process. ROI, Maintenance & Reusability is on the high priority in every Feasibility study of Automation. In this article, we will take a look at one such maintenance problem and how to overcome it using the much-famous Page Object Model. Nowadays, the page object model is a new Test automation buzz word  being asked during Testing Job interviews as well.

Industry is sure moving to Automated Test execution. But as I say – Automation is confirmatory, Manual tests are more exploratory. Only Automation testing is not enough, so testers need to be good at finding bugs. “Finding Bugs” is one characteristic that differentiates a good tester from a mediocre tester. The basic principle is to combine things that programmers didn’t expect with common failure modes of your platform. Always remember, Testers don’t break the software. It is already broken. You just need to find those broken pieces and help make the software better.

Machine learning is a buzzword in the technology world right now, and for good reason: It represents a major step forward in how computers can learn. Whether you realize it or not, machine learning is one of the most important technology trends – it underlies so many things we use today without even thinking about them. Speech recognition, Amazon and Netflix recommendations, fraud detection, and financial trading are just a few examples of machine learning commonly in use in today’s data-driven world.

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…

Get Started with Studio

Get Started with Studio

Follow STS

Stay updated | 1500+ Users

Name

Email*

S/W Testing Studio Archives

S/W Testing Studio Archives

About STS

Software Testing Studio is an attempt to share some incredible knowledge from industry leaders & experts, which should be helpful for anybody to start his/her career in ‘Software Testing’ or to progress it further. Apart from the technical nitty-gritties, one can also find some intellectual posts by industry experts sharing their Wisdom.