Wednesday, June 10, 2009

Roles and Responsibilities of a "Software Testing Engineer"

Generally Roles and Responsibilities of a Testing Engineer may vary, depending upon the working company. But here we are going to discuss about the general and important roles and responsibilities of a Testing Engineer.

1) Analyzing the Requirements from the client
2) Participating in preparing Test Plans
3) Preparing Test Scenarios
4) Preparing Test Cases for module, integration and system testing
5) Preparing Test Data’s for the test cases
6) Preparing Test Environment to execute the test cases
7) Analyzing the Test Cases prepared by other team members
8) Executing the Test Cases
9) Defect Tracking
10) Giving mandatory information of a defect to developers in order to fix it
11) Preparing Summary Reports
12) Preparing Lesson Learnt documents from the previous project testing experience
13) Preparing Suggestion Documents to improve the quality of the application
14) Communication with the Test Lead / Test Manager
15) Conducting Review Meetings within the Team

These are the Roles and Responsibilities of a Testing Engineer which is based upon my knowledge. If you know more about this kindly write it down in the comments section.
Your Feed backs are welcome!

52 comments:

  1. Hello,
    I agree with you in most of items.
    In my opinion, based on my experience, basically, in the item 5 the Software Testing Engineer would especify, support and make sure that test data would be available in quality and quantity enough at the reuired time.
    I would suggest to add the participation of Software Testing Engineer in the decision of acceptance criteria, exit criteria, resumption criteria of the tests, and participate in the go-nogo meeting.

    ReplyDelete
  2. I agree with most of these points, but in what world does the test engineer have any control over the test environment? In 10 yrs of testing, I've never had the ability to enforce code freeze or scope creep. That takes buy in from senior management down to the developer level and we all know what scoundrels developers are :)

    ReplyDelete
  3. I too agree with the points mentioned,add to this there is domain expertise which is needed by a Tester, understanding the customers operational area and then trying to simulate the business scenario always adds value to the work one does.

    I always felt that in my career of last 5 yrs, inclination towards domain and customer operational areas have added value to the customer and made the Dev folks to depend on QA.

    ReplyDelete
  4. I am agree with u but i have some more points, which is follows ---
    Design comprehensive test plans.
    Maintain and execute manual tests.
    Enter reproducible defects into our bug and issue tracking software.
    Support defect resolution by demonstrating bugs to the development team.
    Follow-up and verify resolved defects to ensure nothing slips into the live environment.

    ReplyDelete
  5. Good one mi8... i agree with your points. Maybe we can include the diff tools as well

    ReplyDelete
  6. tnx for giving me this opportunity to for gaining some knowledge on testing role and responsibilities.........once again tnx to one and all of you.....

    ReplyDelete
  7. k everything is fine but i think analysing the client req will be done by BA team...am i right

    ReplyDelete
    Replies
    1. Yes, QA would not be in direct contact with client. BA is his client

      Delete
  8. There are few points i want to discuss:-

    1) Preparing Bug Report and submit it to any tool(whichever is used by your organization).
    2) Deciding the Severity and Priority of Bugs.
    3) Preparing work done and when document.
    4) Regularrly search Internet for new testing Techniques and impliment them.
    5) Knowledge Transfer is Must tell others whatever you have learnt

    ReplyDelete
    Replies
    1. Regularly not Regularrly
      Implement not impliment

      Delete
    2. Please check your Syntactic issues,
      1.Regularly not Regularrly.
      2.Implement not impliment.

      Delete
  9. I will agree with you.hope every tester should know this...

    ReplyDelete
  10. Analysation of requirements is belongs to Business analyst responsibility.

    ReplyDelete
  11. ya , what you have said is right,but need some more

    ReplyDelete
  12. it is very help ful for me thank you

    ReplyDelete
  13. thanks prakash and comments gived by all... without discussion we can't know what r the roles for tester because it's depends up on company

    ReplyDelete
  14. its good but Tell about ur work Like Testing Functionality, Black Box, Integration, Regression, System, Acceptance, validation and Verification Testing types mention,

    ReplyDelete
  15. Another one important activity is involved in to the change management activity to implementation for adding new module. Before going to add new module to analysis the impact analysis.

    ReplyDelete
  16. Thnks all .......Gud suggetions...

    ReplyDelete
  17. Perfect for building a resume.. Thank u very much

    ReplyDelete
  18. yes i also agree with this role and responsibility it helps me attained the interview

    ReplyDelete
  19. i also like the suggetion it is so useful to all thanx dude

    ReplyDelete
  20. Its valuable information...thanks

    ReplyDelete
  21. Thnx for ur information.It 'll useful for each and everyone Test Engineer.

    ReplyDelete
  22. Thanx For Ur Info its very useful for us

    ReplyDelete
  23. Really nice post and has been proved fruitful

    ReplyDelete
  24. Thanks for such a wonderful lession. Its gonna very helpful for me.

    ReplyDelete
  25. Really very good points to remember Thankyou...

    ReplyDelete
  26. Responsibilities of Test engineer.
    1) Analyzing and understanding the requirements.
    2) Understanding functionality of feature.
    3) Creating Test case and test scenarios.
    4) Checking functionality of feature, executing test cases.
    5) Creating and Reporting reproducible bug sequence and storing in Bug tracking tool.
    6) Working with Dev team to fix the bug.
    7) Retesting the fixed bugs to check for existence and to check for its effect.
    8) Update the Status of Bug in Bug tracking tool.

    ReplyDelete
  27. Good one thank u very much

    ReplyDelete
  28. Thank u very much for giving RR of testing

    ReplyDelete
  29. Testing is all about detecting bugs in software and making sure developers have fixed the bug before software hits production.

    ReplyDelete
  30. Creating Test case and test scenarios.
    Checking functionality of feature, executing test cases.
    Creating and Reporting reproducible bug sequence and storing in Bug tracking tool.

    ReplyDelete
  31. Creating Test case and test scenarios.Checking functionality of feature, executing test cases.
    Creating and Reporting reproducible bug sequence and storing in Bug tracking tool.

    ReplyDelete
  32. Very helpful information for tester

    ReplyDelete
  33. It Is useful for become a Tester and agree with good points thanks for this share

    ReplyDelete
  34. i agree with these points .this helpful for all test Engineers and main useful fresher

    ReplyDelete
  35. Very helpful information..

    ReplyDelete
  36. Its Very Helpful to get all the responsibilities in a single place, Thanks For Sharing those above list

    ReplyDelete
  37. Thank you very much for sharing this..

    ReplyDelete
  38. I'm not sure exactly ᴡhy but this web site is loading
    very slow for me. Is anyone else having this issue or
    is it a problem on my end? I'll check back later and see if thе probⅼem
    still exists.
    take a look at the site here : How To Password Protect Folder

    ReplyDelete
  39. Ohhhh...Its really awesome article...Really helpful for me and all the users..Following article will be helpful which will give you information about software testing interview questions for SQL:
    http://www.complexsql.com/sql-interview-questions-for-testers/

    Thanks for sharing this article...

    ReplyDelete