How To Archive

3

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 software testing life cycle but it is also important to be able to explain the theoretical aspects such as the benefit of adopting V model as opposed to waterfall methodology.  The following is a list of most commonly asked questions:

  • knowledge of test level mostly unit testing, component testing, integration testing, system testing and user acceptance testing (UAT)
  • test types for each level can be functional, non functional, negative testing, performance, usability, compatibility testing .. etc
  • V model is all about testing as early as possible as opposed to waterfall model at the end of project life cycle
  • how to relate your experience to the position you are applying for.  It is very important to do this right by following STAR method (Situation, Task, Action and Result) to explain your potential employer that you have relevant experience for the position.
  • what test approach you have done in the past.  As for me risk based analysis is the preferred approach in requirement driven testing.
  • how and when to start automation testing.  To me this comes down to how much time is spent on developing and maintaining the automated scripts versus time saved if the test cases done manually for a period of time.  It is usually good idea to wait until closer to the end of complete system where changes are minimum.

In summary, career in software testing is similar to other professions requires specific knowledge and experience.  You are expected to be able to explain the areas listed above during the interview in addition to your practical experience and communication skill.

4

How to write a test plan

Test plan provides an overview of testing approach, resources and schedules of the intended testing activities.  Test plan is usually written in conjunction with test strategy.  It is recommended that you read How to write a test strategy before continuing reading this article.

Test strategy outlines different test levels to be carried out for example 1) Component Testing 2) Integration Testing and 3) User Acceptance Testing for standard 3-tier business layer web application.  Test plan however provides the details of test activities for each test level outlined in test strategy.  The required information for writing test plan are (if applicable):

  • System architecture outlining the whole system from user interface, logic or business layer and database
  • Project schedule i.e. what will be developed per iteration
  • High level of requirements, use cases and features to be implemented.. etc.

the content of test plan documentation will be covering these areas:

  • What features to be tested
  • What features will be excluded or partly included
  • Entry and exit criteria (you can also add suspension and resume criteria) for each test level included in Test Strategy
  • Assumptions and constraints
  • Testing schedules
  • Test deliverables i.e. test scripts, weekly reports, test plan and test sign-off report
  • Defect management work flow and template
  • Priority classification.  Requirement Driven Testing uses priority to select test cases to execute.
  • Severity classification for defects
  • Project and product risk(s)
  • Testing resource
  • Testing environment information.. etc


Dear readers,

We received a large number of emails for test plan template.  You can now get a copy in Word Document emailed to you instantly.  I trust this template will add value to your organization and save your time.  Feel free to contact us if you have any feedback.


4

How to write a test strategy

The purpose of writing test strategy is to outline the strategic plan how test effort will be conducted for the project.  This is usually done at the beginning of Project Development Life Cycle (SDLC) where high level system architecture and processes are being identified.  some examples of documentation required for this document are:

  • What is the project scope i.e. what business function to be delivered
  • System architecture i.e. 3-tied business logic and/or integration with other new or existing system locally or remotely

The scope of test strategy focuses on the following areas:

  • Scope outlining goals, test processes such as defect management, team responsibilities including Business Analyst, Project Manager, Release Manager Developer and Tester
  • Outline a mechanism for handling and responding to feedback from stakeholders on testing progress and outcomes
  • Provide guidance to stakeholders involved in testing

When writing a test strategy the following aspects should be considered:

  • Testing objectives
  • Testing guidelines
  • Testing approach i.e. Requirement Driven Testing
  • Roles and responsibilities
  • Levels of testing
  • Test requirements i.e. test artifacts such as functional specifications, acceptance criteria and test scenarios
  • Test deliverable
  • Entry and exit criteria
  • Defect management i.e. what to do when a defect is reported
  • What test reports will be provided
  • Test environment information and migration procedures
  • Test Constraints
  • Test Risk including project and product risks


Dear readers,

You can now get a FREE copy in Word Document emailed to you instantly. I trust this template will add value to your organization and save your time.


Related Posts Plugin for WordPress, Blogger...