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.
A burndown chart is a graphical representation of work left to do versus time. It is very simple, easy to explain and understand. It is often used in agile software development methodologies such as Scrum. However, burndown charts can be applied to any project containing measurable progress over time. Outstanding work can be represented in terms of either time or story points. When tracking using the Burndown chart, teams can use a sprint Burndown chart and a release Burndown chart. It is one of the most important artifacts and a fundamental metric in agile scrum.
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.”
The phrase mobile commerce was originally coined in 1997 by Kevin Duffey – “the delivery of electronic commerce capabilities directly into the consumer’s hand, anywhere, via wireless technology.” Mobile commerce transactions continues to grow, and the term includes the purchase and sale of a wide range of goods and services, online banking, bill payment, information delivery and so on. Also known as m-commerce.
Everything is not easy at the beginning. Once you start your Selenium automation journey, you will frequently encounter certain exceptions in Selenium WebDriver. But don’t worry, we got you covered. It’s good to have a basic knowledge about 11 of the most common Exceptions in Selenium WebDriver which you may / may not encounter during the course of your test automation.
Simply stated – Within an agile development project, the Sprint Backlog is a document that lists the tasks to be performed as part of a Sprint. During Sprint Planning Meeting, the User Stories, which are approved, estimated, and committed, are taken up for discussion by the Scrum Team. Each Scrum Team member also uses Effort Estimated Task List to select the tasks they plan to work on in the Sprint, based on their skills and experience. The list of the tasks to be executed by the Scrum Team in the upcoming Sprint is called the Sprint Backlog.
Static, as in Stationary or Stagnant. What do you think is stationary in software terms? Yeah! The code. Either it can be stationary – or running, i.e. when you run the code. As the name suggests Static Code Testing is one of the software testing technique where the code is stationary, i.e. NOT running. How? Simple, you don’t execute any functionality (or code). Then how does it ‘test’ the system, you may ask 🙂 In Static Code Testing we don’t execute the code, instead it is checked manually or via tools for any design defects. As you might have guessed – Static Testing is not just limited to the code, we can even analyse the associated documentation like requirement & design documents to identify any potential errors or standard violations. Static testing is also known as Dry run 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…
Software Testing Levels, Test Data, Waterfall methodology, Agile Scrum, HTML Elements, Selenium Automation, WebDriver, Test Data Management, Scrum methodology
I first heard the term ‘Monkey Testing’ from a developer when I was 1 year old in IT industry. The developer was quite friendly & wasn’t confident enough about his code – “Hey, let’s do some Monkey Testing” he said. He sat with me and that was my first experience with practical Monkey Testing. Yeah! The name sounds funny, but this technique surely works (if you know the impacted areas). In this article let’s explore ‘Monkey Testing’ in detail.
The basic rule of testing is to always take screenshot to base your claim. You can take screenshots at any stage of the test, but mostly, it is used for when a test fails and taking screenshots helps the analysis so we can see what went wrong during a test failure. The bugs you log should always have a screenshot attached to it. However, it is not necessary that screenshot should be taken only when you encounter a situation where expected result does not match the actual result. Screenshot are also taken as a proof that things are working fine. In this tutorial we will learn how to capture Screenshot in Selenium Webdriver using Java, i.e. TakesScreenshot class.
Requirements analysis is an important aspect of software testing. On many traditional projects, this was devoted solely to Business Analysts, who worked closely with their clients to build out a framework onto which development could be executed. With an effective agile project, Quality Assurance engineers should also be part of this phase who can provide significant value. The software code, doesn’t matter how well it’s written, can’t do anything if there are ambiguities in requirements. It’s better to catch the requirement ambiguities and fix them in early development life cycle. It’s a fairly well established theory that the later in the software development life-cycle an issue is discovered, the more expensive it is to fix, and that most often, this cost growth curve is exponential rather than linear. So it’s important to have requirement analysis and catch these incorrect requirements before design specifications.
Convergence of Social Media, Mobile, Analytics, & Cloud [SMAC] is one of the hottest trends these days. It is a major business agenda forcing organizations to rethink their strategies and increase technology investments in this direction. Combining Mobile and Analytics, let’s see how Mobile Analytics can help strategize our testing approach!
Recognize that the data is important, but understand what it means. While raw data is important, it’s the organization and utilization of the data – the analytics – that really drives the push for mobile app companies to continuously strive for application optimization. A lean comprehensive overview of all of the aspects of your app in a quick and efficient manner helps you strategize the Testing solution.
Continuing on our SQL Interview Questions and Answers series for Manual Testing,
Add a record to table, Add a column to a table, How to change value of the field, How to find unique values, Find names starting with ‘A’, Fetch alternate records from a table, How to display current date, Difference between SUBSTR and INSTR, Select random rows from a table, What is Case Function, How to find second highest salary, How to find third highest salary or nth highest salary!
Scrum, the most popular agile framework in software development, has at its core the agile sprint — the scrum term for iteration. It is a short, consistent cycle no longer than four weeks. The goal is to have an iteration short enough to keep the team focused but long enough to deliver a meaningful increment of work. The agile sprint begins with Planning and ends with Review & Retrospective. Each day of the Sprint is marked by a brief meeting called the Daily Scrum or simply, Stand-up.