What are the qualities of a good tester?

The quality of the software testing depends up on the skills of the tester since the whole software testing process revolves on the instructions of the tester. Even a single wrong decision can cause the whole testing process go wrong.

A tester makes a decision based on his testing skills and capabilities. So a tester has to be very careful while taking any decisions regarding the software testing process.

ATTRIBUTES OF A GOOD TESTER

1. GOOD TECHNICAL & PRACTICAL KNOWLEDGE
- It is not necessary that a good tester might be an experienced one.
- A fresher having good technical and practical knowledge about the software testing methodologies and strategies can also perform effective software testing. - Though one learns from experience, it is often seen that there are many testers who even after having much experience are not able to carry out the software testing process efficiently in a well mannered way.
- They often keep bumping into the problems.

2. KNOWLEDGE ABOUT TESTING PROCESS
- A good tester keeps the overview of the whole testing process in mind while drafting out the test plan.
- He/ she include all the aspects to be tested in the test plan.

3. FAULT FINDING
- He insists on finding the faults earlier in the software system or application since discovering the bugs and errors in the earlier phases of the development helps a great deal.
- It takes less effort to fix a bug or an error in the initial stage of the development when compared to the efforts required in the later stages of development.

4. KNOWLEDGE ABOUT COMPUTER PROGRAMMING
- Testers know computer programming well.
- They are capable of maintaining good credibility with the fellow programmers.
- They have senior computer programmers working over them.

5. KNOWLEDGE ABOUT APPLICATION SOFTWARE
- They know the application software under testing very well.
- He/ she should be able to exploit the application software like an end user.
- Thinking like a user open ups new ways in which the application can be used.

6. SMARTNESS
- Good testers are really smart people and know how to exploit the application.
- Their intelligence is at par with the programmers.

7. NOTICING THINGS
- Good testers tend to notice those minute and little things that do not come to the notice of the other people.
- They keep a sharp eye on the behavior of the program.
- Even a little unusual happening can be an indication of a bug or error.

8. HANDLING CHAOS
- Obviously when a team comprising of people at different designations there will be a lot of chaos.
- Handling such chaos depends on the individual character.
- A good tester is expected to have good tolerance capacity or we can say he/ she should have patience.

9. HANDLING CRITICISM
- Testers have to suffer a lot of criticism from the programmers.
- A tester having good sense of humor can easily get through such a trap.

10. TENACITY
- Another social skill called tenacity is found in good testers.
- Tenacity is the ability of an individual to compromise with the opinions of the others.
- A good tester knows how to socially smart and is a good diplomat.

11. KEEPING TRACK
- A good tester keeps a track of his testing.
- He/ she keeps his observations organized.

12. SKEPTICAL NATURE
- A good tester is a bit skeptical.
- He/ she do not takes anything for granted and questions every thing suspicious for bugs and errors.

13. TOUGH
- A good tester is tough since he/ she has to suffer a lot of criticism and questions of the programmers.

14. SEARCHING NEW WAYS
- They are always searching for new ways of testing an application.
- They are technology hungry. Testing is quite a laborious task.

15. HONESTY
- Finally a good tester is honest with his duty and doesn’t follow any corruption.

What are different characteristics of documentation testing?

Though the term documentation is used is various different ways, it is usually used to refer to the process of providing the evidence.
- Documentation is very important and useful.
- It also refers to the process of the documenting the knowledge about a software system.
- But in the context of software engineering, documentation refers to the process of writing the software documentation.
- Individuals or the professionals who carry out the process of writing up of the software documentation are called documentalists.

Every documentation has to follow up a composure called documentation composure. According to the document composure it should include the following:

- Written information and instructions for any technical or projection performing,
- Data and media of any kind of format and details about the reproduction.
- Other related content.

Today documentation about any software system or application is available in many formats like user guides, user manuals, online help, white papers and quick reference guides. Nowadays documentation in hard copy is rarely seen.

- The documentation for software systems or applications is distributed to the open public via software products, on- line applications and websites.
- Certain principles are followed while preparing the documentation for the software or the hardware product.
- Documentalists always compulsorily follow the ISO standards.
- These standards are not available for the general public.
- Apart from principles, certain guidelines are also to be followed regarding the documentation.

The procedure for preparing a perfect documentation involves the following steps:
- Document drafting
- Formatting
- Submitting
- Reviewing
- Approving
- Distributing
- Repositing
- Tracking

Production of documentation involves contribution from corporate communicators and technical writers since the technical writers have an expert knowledge about the software and also they are good at writing contents. They are able to design the information architecture. They are able to easily cooperate with the SMEs or subject matter experts (who are none other than software developers, engineers and also other people like clients and customers) to prepare the kind of documentation the users need.

In the field of computer science, there exist the following types of documentation:

- RFP or request for proposal
- SOW or statement of work or scope of work
- Requirements
- System design and functional specifications
- Software design and functional specification
- Change management
- Error tracking
- Enhancement tracking
- UTA or user test and acceptance

Nowadays many kinds of software applications are used to create documentation. But, SDF or software documentation folder is the most used software application used by the engineers to create the documentation for the software system or application.

While the development of the software system or the application is in progress, the software engineers keep a written record detailing the build of the application which essentially includes an interface section, a requirements section in order to provide more details about the communication interface of the software system or application.

- Usually a notes section is provided giving the details about the proof of the concept, tracking errors and enhancements.
- Apart from this a testing section is also included to give the details about how the software system or application was tested.
- The documentation confirms to the requirements and specifications stated by the client or the customer.
- The final documentation is a detailed description of the build and design of the software.
- Apart from this, it lays down the instructions for installing and uninstalling the software.
- Documentation testing is thought of as the most cost effective testing.
- Any discrepancy in the documentation will cost too much.
- The documentation is tested in a variety of ways to check the degrees of the complexity of the software system.

Project Management - The W5HH Principle

Barry Bohem suggested an approach that addresses project objectives, milestones and schedules, responsibilities, management and technical approaches and required resources. This is called W5HH principle. The questions that are answered in this principle are:

- Why is the system being developed?
- What will be done by When?
- Who is responsible for a function?
- Where are they organizationally located?
- How will the job be done technically and managerially?
- How much of each resource is needed?

WHY IS THE SYSTEM BEING DEVELOPED?
It enables the parties to assess the validity of business reasons for the software work. It justifies the expenditure of people, time, and money.

WHAT WILL BE DONE?
It specifies the task set required for the project.

WHEN WILL IT BE DONE?
It helps to determine the project schedule. It helps in determining when tasks are conducted and when milestones are reached.

WHO IS RESPONSIBLE FOR A FUNCTION?
It helps to accomplish the role and responsibilities of each member of the software team.

WHERE ARE THEY ORGANIZATIONALLY LOCATED?
The software team does not contain all the roles and responsibilities. The customers, users and stakeholders also have responsibilities.

HOW WILL THE JOB BE DONE TECHNICALLY AND MANAGERIALLY?
The management and technical strategy of project is defined once the scope of the product is established.

HOW MUCH OF EACH RESOURCE IS NEEDED?
It helps in deriving estimates based on the answers to the above questions.