Who and why should we take up this certification?   As soon as I saw this certification in Microsoft website, a question arose in corner of my mind – “Is this something to do with Unit, Integration or Load testing? Does it involve coding?” as I am not very well versed with coding. Started digging for the syllabus to confirm can I take up this test? Yes, syllabus does not include anything about coding, it’s just usual testing activity any tester will do on day to day activities in Microsoft Test Manager and not really Microsoft Visual Studio which may think of.  One may be using Microsoft Test Manager for a long time, however taking up this exam may unveil some of the stuffs we don’t really know as it happened to me. I was using this Microsoft Test Manager for nearly 8-10 months with simple approach, but I learnt more in a month when I was preparing for the exam. Also, having this certification will add into our profile which is quite important in consultancy service in...

Agile certification was one in my bucket list from some time. But couldn't find any well recognized board certifying this. When  ISTQB  announced this certification, I soon made a decision of taking up this. As usual, starting digging for syllabus and books. When I took up the exam back in March 2015 there wasn't much info on this. However bought  a book  from Amazon, which is suggested in the ISTQB website, started reading this.    Book contents/syllabi are fairly easy to understand and not much to read upon. So after reading the book once I decided to take up the exam. But, I must say that this was one of the most confusing testing exams I have ever given. Questions were simple but multiple choices were very confusing. I narrowly passed the exam. My advice is if any one willing to take this exam, attending a training course is not a bad idea.   Unfortunately, apart from the above book I do not have any other content to share.

Priority and S​everity are often the shaken debatable concepts and are almost​ interchangeably used between different people even within the test team. They both are attributes of a bug/defect and play important role in fixing the bug. ​Below I have put in some information which I have gained through experience and reading many blogs over many many years. Hoping this helps to clear confusions (atleast few) any individual may have: What is Severity?​ Severity is an attribute which denotes the implicatio​​n of a bug/defect on the system – how critical the defect is and what is the impact of the defect on the system?. Impact is defined in terms of financial loss, damage to an environment, company’s reputation and loss of life​ etc​​. Severity is an attribute which is set by the tester. Different Levels are: 1. Critical / Show Stopper (S1):  A defect that completely hampers or blocks testing of the product/ feature ...