Skip to main content

Seven Principles of Testing

According to the ISTQB there are seven principles of  testing. They are ,

  • Testing shows presence of defects: Testing can show that defects are present but it is not the proof of correctness of the software product. Testing cannot find out all defects there can be many bugs remain in the software.
  • Exhaustive testing is impossible: Testing all combinations of the software is not possible. It focus on critical and most important business functionalities which means it prioritize risk clustered areas.  Testing involve in mitigating the risk of the application. 
  • Early testing: Testing should be start with as much as early actually it should start withe strat of SDLC (software development life cycle). 
  • Defect clustering: A small number of modules or areas contains most of the defects found during the pre-release testing or shows the most operational failures. 
  • Pesticide paradox: If same set of test cases run again and again but won't able to find bug further then need to revise and review test cases regularly also need to write test cases to exercise different paths of the software.  
  • Testing is context depending: In real world testing is depend on the context. For an example the way of testing banking application and human resource application is different because banking application is much concern on security and HR application does not
  • Absence – of – errors fallacy: If the software built is unusable and does not meet the user’s needs and expectations then finding and fixing defects does not help. Therefore first attempt of a test engineer should be to check the built and expected are match each other. 


 

Comments

Popular posts from this blog

Accessibility Testing

Accessibility Testing is a non-functional testing type. This means anyone can use a particular web application, mobile application, website, or any other software package. Any human means not only perfect men or women but also differently able people as well. Things can be used for testing, 

Differences between Severity ,Priority and Status

In market there are many bug tracking and project management tools available. These tools allow us to keep essential information of a bug or task. You will see there are three places have to fill when key in a task. Those three places are Status, Priority and Status of a bug/task. Let's see what those stand for.  Severity Priority Status Connotation Severity of a bug means how much it affecting to functionality of the software. Total damage it can do. Priority means how fast a bug or task should be resolve. Status means the current position of the bug/task. Types            Critical            Major            Moderate            Minor           Cosmetic           Low           Medium           High           New           Active/Open           Resolved/Fixed           QA In progress           Reopen           Closed/Completed 

MVC Architecture

Model-View-Controller (MVC) is a design pattern recently most popular among software engineers for applications which are needed to provide multiple views with using same data. I am suggesting MVC is better than WCF, because of this module separation. For an examples       ·          Multiple views and controllers can interface with same model for modification even those never exist before add this model.       ·          It is supporting all type of HTML verbs.       ·          No view state and post back events.       ·          Easy integration with JavaScript framework.       ·          Helps to decrease complexity of project       ·          Provides RAD development ( http://en.wikipedia.org/wiki/Rapid_application_development ).