Tester Trait
Being a Tester is not an easy task. As a test engineer you are responsible for the quality of the product that your organization makes. A good test engineer is always valued by the organization.

Test engineers should certainly have good technical knowledge, testing skills, interpersonal skills and domain knowledge.

On this page we will explore different ways of

  • How to become a better test engineer?
  • How to become more effective and efficient in our day to day test activities?
  • How to add more value to the organization?


Involve early
You should get your self involved in the project in the inception phase. Even if you are placed in the project which is already in the development phase you should get all the requirement documents, design documents and functional specification. You should also make your self familiar with the tools related to requirement management and UML modeling tools. Try to read as much as you can from these documents and ask the right questions. This will make your understanding of the product better and along the way, you will also build good repo with dev team.

Domain Knowledge
Test engineers are closest to customer in any organization in terms of what to expect from the product. Being a test engineer you should try to get as much domain knowledge as you can for your product. If you are working on a product for insurance agents, you should have very good knowledge of insurance sector, terminology used in their field etc. This is certainly a long process, but this can go a long way in you becoming a better tester and more knowledgeable than your fallow dev counter part. You can build this knowledge by your own or you can ask your organization to arrange customer visit, training etc.

Technical Knowledge
Being a test engineer does not mean that you do not have to be tech savvy. In fact it is very critical for you have good understanding of operating systems, databases, software modeling and scripting languages at the minimum. Knowledge of modeling will help you in understanding the system, knowledge of operating system and databases will help you in identifying the defects on these layers and scripting languages will help you in writing small utilities that will make you more efficient.

Tool Usage and Automation
As a test engineer, you will have to do lots of repetitive work and you should try to take as much help as possible from the available tools. You should never think that automation is just for test execution, tasks like status reporting, matrix generation, test data generation, test environment creation all these can be automated. Remember what ever time you save by doing automation will be spent on the product and will allow you explore the product.

Learning from Experience
It is very critical for you to learn from your projects, continuously. You should always do postmortem of your project to identify weaknesses in your planning, execution or any other area. Apart from identifying weaknesses, what ever processes you have followed, tools you have used or any other thing that added value to your project should be revisited.

People and communication skills
This is a must for test engineers. You should always work on your interpersonal and communication skills constantly. Being a test engineer, you will be required to interact with developer team, customer and support staff. Your good communication skill will help you a lot. You will also deal with the people issues and deliver bad news like product can not be shipped to the management. All these things required you to have very good interpersonal and communication skills.

Read, Participate and become knowledgeable
This is very essential to keep yourself updated with the latest happening in the industry. Share your knowledge as much as you can by participating in conferences, symposiums and publishing on websites. There is so much information on the net for you to consume, visit regularly to the testing related websites and build your knowledge and network.
Recent Updates
Guerrilla Testing Tips
One CPU better than two
TG Tips For Automation?
Is It Really Done?
Exploratory Testing
Automated Testing
Model Based Testing
Live News
 
Read More
Accessibility API Testing Article Backword BigBang Blackbox Blog Bottomup Boundary CaseStudies Certification DefectReport DistanceTest Equivalence FitNesse Geeks Graybox Guerrilla Testing Tips GUI HTA Humor Hybrid Internationalization Installation Integration Is it done? JUnit Measurement Mercury Quality Centre News One CPU better than two Patent Performace Checklist Rational Test Suite Regression Requirement Verification Research Rational Functional Tester Security Selenium SilkTest System Testing Templates TestComplete Tools Testing Types Testing Tools In News Testing Terms In News Testometer Test Plan TG Tips For Automation Top Down Integration Trait UAT UI Testing CheckList Unit Testing Usability VMWare Web Application Security Web Application Testing Checklist Whitebox Testing
Disclaimer  |  Privacy Policy  |  g e e k AT T e s t i n g G e e k DOT c o m
© Copyright 2008, www.TestingGeek.com