Programming is integral to IT, and automation is no different. What interviewers are looking for is if you can think of the correct logic or algorithm. It gives them an idea about your logical thinking prowess.
Most of the times people are not afraid of too much work or learning something new or stretched working hours. What’s frustrating is the messed up work, not too-much work.
Defect tracking is a testing-critical strategy that QA engineers utilize to understand the loopholes in the product’s quality and what further improvements it requires to reach the desired results. Software testing has to be intuitive and vast, and thus it has to be logical and yields measureable results. That’s the reason why the success of SDLC greatly depends on accurate bug tracking. In this domain, a fine defect tracking tool is crucial in software testing activities to streamline bug reporting, while accelerating delivery silos.
Recently one of my LinkedIn discussion gained much traction. Although I don’t know the reason – may be it was uncommon OR way too common among testing enthusiasts. The post got reactions from the who-and-who of the QA world – ranging from Testers to Managers up to VP Products. So thought of sharing the insights to a larger audience via a blog post. In this article, we will look at the options available to a QA team if there are ‘way too many’ defects in the application. Here we go…
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 fourth set of JDs talk about…
As soon as you write Selenium Automation in your resume, interviewer is bound to give you a sheet of paper & ask write a Java program. Though Selenium doesn’t require extensive Java knowledge but still there is a set of basic Java programs that you should be able to write on-the-spot. Continuing on our Java interview series for Selenium Automation, this article covers five of the common Java Sort programs frequently asked in the basic technical interview. The questions are easy, but don’t forget to mark these java programs in your to do list before attending any entry-level technical interview for Selenium automation testing.
Exploratory Testing has gained popularity in past few years. There are several studies and has also received much of professional attention from the industry. Exploratory Testing gives power to the tester together with responsibility; it offers great freedom and opportunity to the tester for exploring and identifying areas for improvement. But why do we need exploratory testing if we’re already doing a good level of scripted testing? We’re writing test scenarios in each story, running them on different builds until they all pass, and we’re also running them in regression to make doubly sure that the product is still working. Sound good and thorough – what’s the point in doing more software testing on top of that? Well, there are a few good reasons to do exploratory testing in addition to the regular, scripted testing. It exposes the underlying issues within your product, app or website and allows testers to literally explore the functionality.
FinTech, a buzzword today. Though it has been around from the start of 21st century, recently it has gained unprecedented momentum. Why? Due to the emerging disruptive technologies. But what exactly is FinTech? And how it should be perceived as a Tester? What’s the role of a FinTech Tester? What’s the scope of FinTech Testing? These are some of the doubts testers working in the Finance domain come across daily. This article tries to answer these questions in simple terms. The Finance. The Technology. What’s FinTech? The role of a FinTech QA. And its scope. Let’s deep dive…
Yeah! A thought that crosses every tester’s mind who is searching for a better QA opportunity. Why am I not getting selected? Simple! Because you were not the best fit. Best fit in terms of technology, experience, salary, attitude, skills, behavior, etc. Only QA knowledge is not enough to land you a job. Yes, companies look for the ‘Best Fit’ among the available candidates. Some look for tech-savvy candidates, other focus more on the learning attitude. Every company has its own set of guidelines – what we call as company culture. With this article, I try to elaborate on some of the perspectives around Software Testing interview. It has helped me, and I hope this helps fellow testers as well in their quest for the next dream job.
The Software testing community experienced an exciting year of 2017 with many trends taking shape. Applications of artificial intelligence (AI) and automation, continuing trend in adoption of DevOps, increasing test automation, shortening release schedules, and the lack of time for testing. The prevailing state of software testing is getting more challenging with every day passing. With the huge demand for high-quality products within a short time span, the role of testing has grown beyond just another process. Not a single software product could be released without its quality testing and bug fixing. The Software testing industry is always evolving and transforming to new horizons that’s why it’s better to forecast and predict such trends ahead of everyone. This article makes bold predictions for Software Testing trends of 2018.
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.