Two other terms used to describe how software is tested are Static Testing and Dynamic Testing Techniques
Static Testing: refers to testing something that’s not running—examining and reviewing it. During static testing, software work products are examined manually, or with a set of tools, but not executed.
Dynamic Testing: is what you would normally think of as testing—running and using the software.
Software Development Life Cycle methodologies are available for executing software development projects. Although each methodology is designed for a specific purpose and has its own advantages and disadvantages, most methodologies divide the life cycle into phases and share tasks across these phases. Few commonly used methodologies in actual testing:
Waterfall model: is one of the earliest structured models for software development. It consists of the following sequential phases through which the development life cycle progresses:
- Requirement Gathering
- Analysis phase,
- Software Design,
- Implementation and Testing
V model: is an extension of the waterfall model. Instead of moving down in a linear way, the process steps are bent upwards after the coding phase, to form the typical V shape. The V-Model demonstrates the relationships between each phase of the development life cycle and its associated phase of testing. (Its is also know as Verification and Validation model).
Agile model: Agile Methods break the product into small incremental builds. These builds are provided in iterations. Each iteration typically lasts from about one to three weeks. Every iteration involves cross functional teams working simultaneously on various areas like planning, requirements analysis, design, coding, unit testing, and acceptance testing.
Agile model believes that every project needs to be handled differently and the existing methods need to be tailored to best suit the project requirements. In agile the tasks are divided to time boxes (small time frames) to deliver specific features for a release.
Image Posted on Updated on
A software bug is an Defect, Error, Flaw, Failure, or Fault in a computer program or system that causes it to produce an incorrect or unexpected result. Most bugs arise from mistakes and errors made by people in either a program’s source code or its design, or in frameworks and operating systems used by such programs, and a few are caused by compilers producing incorrect code.
Day 2 started in a bit of a blur, as I was trying to still digest the waft of information that I had gained from day 1… Nonetheless, the second day offered just as much fun, information, knowledge, ideas and socializing as the first day!Read More …
“Severity” is how severe the bug is with regards to the system, the user and the business. So this is the impact of the bug that you find, with regards to the system. Whether it is something that has minimal impact, such as a spelling issue in a paragraph of text, or something more severe such as an application or server error screen that appears when more…
“Priority” on the other hand, I interpret to be the importance that the defect is fixed from the business’ perspective. So in effect, this is setting a level of importance in which the defect should be fixed purely from the context of how it affects the business.
Few very important scenarios related to the severity and priority:
High Priority & High Severity: An error which occurs on the basic functionality of the application and will not allow the user to use the system. (Eg. A site maintaining the student details, on saving record if it, doesn’t allow to save the record then this is high priority and high severity bug.)
High Priority & Low Severity: The spelling mistakes that happens on the cover page or heading or title of an application.
High Severity & Low Priority: An error which occurs on the functionality of the application (for which there is no workaround) and will not allow the user to use the system but on click of link which is rarely used by the end user.
Low Priority and Low Severity: Any cosmetic or spelling issues which is within a paragraph or in the report (Not on cover page, heading, title).
A few weeks ago, I was lucky enough to be able to attend Agile Testing Days, which was held in Potsdam, Germany.
My employers bought 2 tickets to the event and put them up for a competition to the test team and I managed to obtain one along with my colleague Paul Coletti.Although we didn’t have tickets Read More ….