How can You Get a Job as Software Testing Engineer

I'll try to help people get info to become a Software Testing Engineer or a Software QA (Quality Assurance) Engineer.

The role of a Software testing engineer is very important in a company as he will be the person in representing on behalf of company is reaching the company's quality product to the customer, in this aspect he will be interacting with the programmer and the customer. He has to have thorough knowledge of the various operating systems, software, and hardware, also should have an in-depth knowledge of software test methodologies and development cycles, of course a good communication skills too.

As its told in my earlier posting that every company will have its own testing strategies and methodologies and few companies may not have which is very essential, hence one must have good knowledge of methodologies. Being a test engineer he should be well versed with the technology and to know what to test. A tester should have creative ideas for creating better test scenario and test cases.

Along the side of the above knowledge a tester should also be a good at documentation. He should be able to create and define various documents needed for defining test requirements. Most of the test documents are needed to be maintained and controlled as most of the customer will demand for the test results at the stage of final delivery of the product, also this document serve as proof of the quality of the product.

Friends here are the few points that make you to be a perfect testing engineer,

1. To be interested in knowing new methods and technologies.
2. To be interested in creating new documents and formats to improve the existing methodologies and technique.
3. Good in finding errors of others.
4. To think uniquely.
5. Really interested in improving the quality of the software.

You will find more testing related info written on this blog which will be updated daily. Keep visiting & reading this daily.

Quality Management System (QMS) - What's this

My dear friends, today I would like to post something related to quality process that starts along with any development activity. Every individual company will have its own QMS (Quality Management System) depending upon its nature of work and process.

What is this QMS?

Quality Management System (QMS) can be defined as a set of polices, processes and procedures required for planning and execution.

In general a QMS will have the following process to manage its development activity effectively.

• Common Process.
• Hardware Process.
• Software Process.

The above process are very important in the development activity as every stage of the development is well defined to meet the standards of the certification that the company has perceived such ISO,CMMi, BVQI etc.
The above process are again defined and approved by the QA Managers to suit their process of development activity, ultimately the aim of QMS to produce a hassle free product.

In the context of either Hardware or Software process, quality measures how well, a Hardware or Software is designed and how well the hardware or software conforms to that design, although there are several different procedure to design and develop the product as specified or required by the customer.

Generally the following things are noted when we closely look at the term QUALITY of a product.

• Reliability
• Understandability
• Portability
• Maintainability
  
• Testability
  
• Usability
  
• Consistency
• Efficiency
  
• Security
  

With consideration of all the above factors, the quality product is delivered to the customer.
Just a hit on to this link every day to have an updates on all the happenings in the industry...

Process before starting a project

Dear Friends, here are the few points that I would like discuss that generally takes place in any of the company before starting the Project and Testing.

1. A project start meeting
2.Get the PRS (Product Requirement Specification) or any other SOW (Statement Of Work) from configuration management tool.
3. Study phase - PRS
4. Validate PRS with respect to SOW
5.Get design doc from developer through configuration management.
6. Analyse requirements and implementation based on PRS and Design Doc.
7. Prepare test cases and formulate ATP(Acceptance Test Plan) .
8.Generate Traceability matrix with respect to ATP.
9. Test setup.
10. Testing and bug filing.
11. Test Report generation.

This is what I have understood when I have undergone a training conducted by my quality team member. All the above steps are to be followed in each phase of the design to make a successful and defect free product.

Am currently working on a project which is basically a network project on Linux OS, with this start again I have to study and understand about Networking, few of the followings which is very important to understand about my current project and that my Project Manager has suggested to read.

1.Introduction to Networking
2.Types of Network

• LAN
• MAN
• WAN
• WLAN
• VLAN

3. Network Topologies
4. Network Operating Systems
5. Network Protocols

The list goes on increasing, I have started to study simultaneously all the concepts together, because it was and is very much necessary for to adjust to the pace of the project, but still I have to know and understand a lot about all these.I have come across many more things which were very challenging to achieve both practically and logically, friends I will write with few such examples in my forthcoming posts.