Skip to main content

What makes better QA

This question is on mind of all QA and QE engineers , As per my experience following will made better QA,

  • Design cases together with team. 
  • Test first.
  • Be more technical. 
  • Be on definition of done.
  • Touch it , feel it and sense it.
  • Ability to code review.
  • Responsible. 
  • Monitoring and assisting operation works. 
  • Be knowledgeable on the domain.
Labels:

Comments

Post a Comment

Popular posts from this blog

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       ...
1 comment
Read More »

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       ·          P...
2 comments
Read More »