Software QA/Testing Technical FAQs

Part:   1  2  3  4  5  6  7  8  9  10  11  12  13  14  15  16  17  18  19  20  21  22  23  24  25  26  27  28  29  30  31  32  33  34  35  36  37  38  39  40  41   42  43  44  45  46  47 

What's the difference between Alpha, Beta and User Acceptance testing?

The focus in this question is somewhat wrong. You don't do Alpha testing, you do testing against the Alpha cycle of the software. The Alpha cycle is during the development phase. The product has many defects and is not suitable for users in a production environment to be using. Once the Show-Stopper, Critical and most Major defects have been resolved, and once the majority of planned functionality has been added to the product, a Beta release can occur. It is best to have someone coordinate the beta testers rather than just throw the software out to the general public--this way you can keep track of the defects generated by beta users in the field. User Acceptance testing occurs when you have to deliver your product to a customer based on contractual obligations. The User Acceptance test is usually written by the customer or an agent on their part. It is designed to verify, usually only with positive test cases, that the product is as described in the contract.

How can I be a good tester?
We, good testers, take the customers' point of view. We are also tactful and diplomatic. We have a "test to break" attitude, a strong desire for quality, an attention to detail, and good communication skills, both oral and written. Previous software development experience is also helpful, as it provides a deeper understanding of the software development process.

How to do Laod testing for web based Application?

1. Recording a scenerio in QTP of my web based application.
2. Make 100 copies of that scenerio and run the test (scenerio run for 100 times)
3. In that case, do the load of application on server.
4. The basic logic of running the copy 100 times is to create same scenerio as if 100 users were working.

What is GUI testing? What elements will we cover in GUI testing?

In GUI testing, need to cover the customer requirement if don't have to validate 1. Font size, colors, spellings(labels) etc
2. Every application should follow Microsoft rules like
2.1 Controls should be Initcap (i.e every label should start with Capital letter )
Can observe that in Win applications every label starts with Caps
2.2 OK or Cancel button should exist
2.3 Controls should not be overlapped
2.4 Controls should be alligned properly (left side alignment is mandatory but the right side is optional)
2.5 Controls should be visible
2.6 Short cut keys should be provided
2.7 System menu should exist (i.e if u press Alt key + Space bar a menu will appear at the left most corner )
2.8 Mouse pointer events
Colors, Label Names, Tab Order, Alignment, graphs , Navigation of the software to test in GUI Testing.

What is that column "steps to reproduce" mean in bug tracking?

Answer1:
Well, steps to reproduce are just that: what are the steps you need to take to reproduce the stated problem.
The steps to reproduce (STR) must be as clear as possible, preferably with screenshots and/or test data. The steps should also be definite (so no 'maybe', 'it sometimes works if you do this' type statements).
In the test projects, you've always tried to keep the STR down to a maximum of 5, this to make sure that the problem is easy and clear to communicate to the developers, to reproduce and hence resolve.

Answer2:
Ideally, once you identify a bug - you would need to determine the least number of steps required to reproduce the bug. This would help your developer to reproduce the bug easily on his development environment.

When is a process repeatable?
A process repeatable when we use detailed and well-written processes and procedures; this way we ensure the correct steps are being executed. This also facilitates a successful completion of the task, and ensures the process is repeatable.
A process is repeatable, whenever we have the necessary processes in place, in order to repeat earlier successes on projects with similar applications. A process is repeatable, if we use detailed and well-written processes and procedures. A process is repeatable, if we ensure that the correct steps are executed.
When the correct steps are executed, we facilitate a successful completion of the task. Documentation is critical. A software process is repeatable, if there are requirements management, project planning, project tracking, subcontract management, QA, and configuration management.
Both QA processes and practices should be documented, so that they are repeatable. Specifications, designs, business rules, inspection reports, configurations, code changes, test plans, test cases, bug reports, user manuals should all be documented, so that they are repeatable.
Document files should be well organized. There should be a system for easily finding and obtaining documents, and determining what document has a particular piece of information. We should use documentation change management, if possible.

Part:   1  2  3  4  5  6  7  8  9  10  11  12  13  14  15  16  17  18  19  20  21  22  23  24  25  26  27  28  29  30  31  32  33  34  35  36  37  38  39  40  41   42  43  44  45  46  47