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.
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…
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.
This is one of the most common questions discussed among the Agile Community – What happens with the undone User Story of Current Sprint? Why does this happen? How should you deal with the undone user story? What should become of such stories? What should be done with the product backlog item itself? Should be it split or should it be carried into the next sprint? Should the team receive any velocity “credit” for completing a portion of the story? And how do you prevent it from happening again? This article addresses all of these questions.
While writing this article, I am worried & concerned. Not about this article, nah! But about the future of Software Testing and Software Testers in particular. Recently during an interview drive, I came across a bunch of (yes, maximum of them) so-called Software testers who don’t even know the basics of Software Testing. Leave alone the required practical experience. It felt sad that testers don’t even know the basic QA terminologies, didn’t understand its importance, take it too lightly as a career, are not willing to learn, etc. At one end industry is moving towards Automated QA and on the other hand here we are with a bunch of novice testers for whom even the foundations are shaky.
Knowledge about fundamental Testing concepts is necessary to crack an interview. But now-a-days only knowledge is not enough. Interviews are not just about the theory anymore. Every interviewer is looking for candidates who have practical exposure to different kind of situations and is able to handle them effectively. Most of the companies will have it as one of their selection criteria. And yes, it doesn’t depend on the technology. For every technology there will be situations that an experienced professional knows how to tackle. In this article, we will look at some of the situational FAQ commonly asked in a testing interview. But we will need your help here. It is just a beginning, please comment any situational question that you might have faced in a recent or any past interview. This would help us to collate an informative list for the Testing community.
Tables are one of the primary design tools for HTML documents. Tables allow for greater control over page layout, allowing creation of more visually interesting pages. Table has rows and columns to store the data. I guess 50% IT industry will come to a halt if Microsoft Excel stops working 😉 that’s the importance of tables in organizing data. Search results on many websites are often displayed in the form of table. E.g. try searching for a flight between X and Y on a travel website, what you get is a table of results. There are times when we need to access elements (usually texts) that are within HTML tables. In this article let’s see how to read data from a Web Table using Selenium.
Recently our article “Manual Testing Is NOT Dead, But Manual Testers Are!” got major traction on social channels and triggered a debate in the Testing community. Some say “I have been doing Manual Testing since a decade now, and I am alive” while others approve of the title. Whatever be the debate (or discussion), Manual testers are finding it really tough to cut through the current jobs market. Want a proof? Try an experiment by analyzing the humongous response to a job opportunity posted for Manual Testers with 3-8 years of experience. How to move forward in Software Testing career?
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 programs frequently asked in the basic technical interview. The questions are easy, but don’t forget to mark these java-program in your to do list before attending any entry-level technical interview for Selenium automation testing.
There is no such statement as ‘I am now prepared for the interview‘. When facing a Testing interview no matter how many interview questions and answers you have gone through – there is always more to read Continuing on our Interview questions series, let’s see some more interesting FAQs related to Domain, Software requirements, Agile Kanban, Career in Testing, SMAC Testing, Automation and Selenium Webdriver.
There is no such statement as ‘I am now prepared for the interview‘. When facing a Testing interview no matter how many interview questions and answers you have gone through – there is always more to read 🙂 Continuing on our Testing Interview questions series, let’s see some more interesting FAQs…
Algorithms are the heart of computer science, and the subject has countless practical applications as well as intellectual depth. Algorithms power the biggest web companies and the most promising startups. Interviews at tech companies start with questions that probe for good algorithm thinking.
“An algorithm is a well-defined procedure that allows a computer to solve a problem. Another way to describe an algorithm is a sequence of unambiguous instructions. The use of the term ‘unambiguous’ indicates that there is no room for subjective interpretation. Every time you ask your computer to carry out the same algorithm, it will do it in exactly the same manner with the exact same result.”
There is no such statement as ‘I am now prepared for the interview‘. When facing a Testing interview no matter how many interview questions and answers you have gone through – there is always more to read 🙂 Continuing on our Interview questions series, let’s see some more interesting FAQs…
Software Testing Levels, Test Data, Waterfall methodology, Agile Scrum, HTML Elements, Selenium Automation, WebDriver, Test Data Management, Scrum methodology