Software testing, though complex, is an integral part of any successful software project. On a high level there are basically two methods to complete the software verification & validation – Manual and Automated testing. While both types of testing are beneficial to web application development, there has been a plethora of speculation on whether software testing should be done manually or be automated. Creation of excellent software demands effective and timely quality testing; and in these times of production on the go, the debate continues on the purpose and efficiency of manual vs. automation testing. Each testing method has its pros and cons but the truth is that regardless of which side of the fence you sit on (manual vs. automated), the argument is largely irrelevant; to achieve high quality software and reduced time to market both methodologies are essential. Let’s explore the 19 key consideration…
How do you measure your car’s performance? Or how do you know that it needs a service? Yeah! We have different criteria to measure its health – the mileage, kilometers run, engine & brake oil, etc. For example your car needs a service if its weekly mileage is less than the ideal mileage recommended by the manufacturer. Right? Similarly for any process to be successful in the long run we need some measurements (or metrics). In this article we will learn about Software Testing metrics and how it helps to keep track of Software Test efforts.
Enterprise mobility is a hot topic; every time we turn around another company is in the news. “Going mobile” seems to be the mantra of modern day enterprises. Mobility offers huge opportunities & benefits for Enterprises. Continuing on my previous post “Understanding Enterprise Mobility” let’s have a closer look as to why it’s so important for Enterprises to adopt Mobility? Why is Enterprise Mobility so popular, and what can it do for your Enterprise?
The amount of data that’s being created and stored on a global level is almost inconceivable, and it just keeps growing. The world’s technological per-capita capacity to store information has roughly doubled every 40 months since the 1980s. Data is everywhere – Documents, Smart appliances, Social networks, devices, Internet, sensors, etc. That means there’s even more potential to glean key insights from business information. But how? What actually is Big Data? What does that mean for businesses? Let’s explore…
User stories and Use cases are both used to document the requirements. They both capture features of the system. They’re both used by the development team to construct the best solution. They can be used to organize and categorize requirements. And they can be used as references during testing to ensure that the requirements have been met. While user stories and use cases are similar, they also differ in substantial ways. The difference can be challenging to understand and explain, especially if your team is making a transition from a Waterfall software development environment to Agile and Scrum. Each serves a distinct purpose, and they both have their place on a well-run software project. We will try and cover User story vs Use case in this article…
In earlier post, we learnt how to replicate (or automate) keyboard and mouse actions in Selenium Webdriver. Selenium Webdriver provides an Advanced User Interaction API (including Actions class) which facilitate user actions to be performed in an application, i.e. users can use this API to simulate keyboard and mouse actions in Selenium Webdriver. In this tutorial we will see how to simulate Double click event in Selenium Webdriver using Actions class.
Continuing on our previous article on Verification & Validation – we know that they are independent procedures that are used together for checking that a product, service, or system meets requirements and specifications and that it fulfills its intended purpose. Verification involves all the static testing techniques whereas Validation is more of Dynamic Software testing. But what is Dynamic testing? Dynamic as in lively and active. And when do you think a software is active? Yeah! When users are actually using it.
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.