Featured Posts
  • New to Software Testing? Been in the Software Testing career for a while? No matter how much or little experiences you have, I would like to share with you some things I have learned throughout the years. Regardless of which industry you are in, or the size of your team, the following aspects must be taken into consideration.

    Insights to Software Testing Career

    New to Software Testing? Been in the Software Testing career for a while? No matter how much or little experiences you have, I would like to share with you some things I have learned throughout the years. Regardless of which industry you are in, or the size of your team, the following aspects must be taken into consideration.

    Continue Reading...

  • Going for an interview is always an exciting experience and good opportunity to revise what I know about software testing.  This year I have been lucky enough to get 100% success rate that I got interview and job offer for every application I applied for.  Here I am going to share with you the type of questions and hopefully will help you winning the software testing jobs you are applying for. I usually go through several books just to remind myself what type of software testing questions might be asked.  I must admit that even though I understand the overall...

    How to win job interview in Software Testing

    Going for an interview is always an exciting experience and good opportunity to revise what I know about software testing.  This year I have been lucky enough to get 100% success rate that I got interview and job offer for every application I applied for.  Here I am going to share with you the type of questions and hopefully will help you winning the software testing jobs you are applying for. I usually go through several books just to remind myself what type of software testing questions might be asked.  I must admit that even though I understand the overall...

    Continue Reading...

  • Imagine that you only have hours left instead of days to complete testing.  Does this sound familiar?  No matter how well we have planned for the resources, estimating testing efforts, prepared the test scripts and scenarios, it would be useless if we don't have the time to execute or a testable system.  There are so many factors can contribute to the delay but how do you approach the situation so that critical functionality is tested?

    Software Testing Approach Only Hours Instead of Days Available

    Imagine that you only have hours left instead of days to complete testing. Does this sound familiar? No matter how well we have planned for the resources, estimating testing efforts, prepared the test scripts and scenarios, it would be useless if we don't have the time to execute or a testable system. There are so many factors can contribute to the delay but how do you approach the situation so that critical functionality is tested?

    Continue Reading...

  • As a software tester one of the most difficult questions I get asked is how long does it take to test something?  My mind goes 1) will the system ready for testing 2) will there be any critical defects in the first cycle 3) has development team delivered complete (or near complete) functionality as per specification .. etc the list goes on.  To most people testing is a task to complete but to me it is all about finding as many defects in the shortest time possible. Whether it is for Agile or Waterfall methodology testing work becomes easier when...

    How do you estimate testing efforts?

    As a software tester one of the most difficult questions I get asked is how long does it take to test something?  My mind goes 1) will the system ready for testing 2) will there be any critical defects in the first cycle 3) has development team delivered complete (or near complete) functionality as per specification .. etc the list goes on.  To most people testing is a task to complete but to me it is all about finding as many defects in the shortest time possible. Whether it is for Agile or Waterfall methodology testing work becomes easier when...

    Continue Reading...

  • I have been involved in many ‘Agile” projects with different organizations and amazingly each project was different from another in term of management style, how each team member ‘collaborate’ with each other and documentation style. If you are about to start a new SCRUM team or already implementing SCRUM this article might give you some ideas of potential issues to address sooner than later. Refer to Wikipedia on SCRUM for more details but in general SCRUM shares similar characteristics with Agile methodology emphasizing on the following: Working software is valued more than documentation Team collaboration is more important over contract...

    Lessons learned working in SCRUM methodology

    I have been involved in many ‘Agile” projects with different organizations and amazingly each project was different from another in term of management style, how each team member ‘collaborate’ with each other and documentation style. If you are about to start a new SCRUM team or already implementing SCRUM this article might give you some ideas of potential issues to address sooner than later. Refer to Wikipedia on SCRUM for more details but in general SCRUM shares similar characteristics with Agile methodology emphasizing on the following: Working software is valued more than documentation Team collaboration is more important over contract...

    Continue Reading...

  • Software testing is a process of finding defects to ensure that the system being developed meet the requirements. In most cases it is likely that some of the requirements are changed or become obsolete. Therefore it is very important to always work from requirement to select which test to execute. Quite often not all test cases are up to date. Working from requirement will ensure that the they are reviewed regularly. Existing requirement and test cases might be updated, removed or added during each review. Requirement Driven Testing (RDT) is project methodology independent test approach that can be used in...

    Introduction to Requirement Driven Testing (RDT)

    Software testing is a process of finding defects to ensure that the system being developed meet the requirements. In most cases it is likely that some of the requirements are changed or become obsolete. Therefore it is very important to always work from requirement to select which test to execute. Quite often not all test cases are up to date. Working from requirement will ensure that the they are reviewed regularly. Existing requirement and test cases might be updated, removed or added during each review. Requirement Driven Testing (RDT) is project methodology independent test approach that can be used in...

    Continue Reading...