QA Testing Questions

QA stands for QUALITY ASSURANCE. QA team assures the quality by monitor the whole development process. QA tracks the outcomes and adjusting process to meet the expectation.

The role of Quality Assurance is discussed below:

- QA team is responsible for monitoring the process to be carried out for development.

- Responsibilities of QA team are planning testing execution process.

- QA Lead creates the time tables and agrees on a Quality Assurance plan for the product.

- QA team communicated QA process to the team members.

- QA team ensures traceability of test cases to requirements.

The Bug Tracking System role is discussed below:

- Testers and developers can know the status of the bug at every stage.

- Changes to the Status will be available to all team members.

- Developers and Testers can easily interact with bugs.

- Repetition of bugs will be avoided.

- Easy to distribute the bug among the developer.

- It will act as a centralized one for defects.

Parallel/audit testing is testing where the user reconciles the output of the new system to the output of the current system to verify the new system performs the operations correctly. Let us say, for example, the currently software is in the mainframe system which calculates the interest rate. The company wants to change this mainframe system to web-based application. While testing the new web based application, we need to verify that the web-based application calculates the same interest rate. This is parallel testing.

EX:

- High Priority and Low Severity:

Company logo is not properly displayed on their website.

- High Priority and High Severity:

Suppose you are doing online shopping and filled payment information, but after submitting the form, you get a message like "Order has been cancelled."

- Low Priority and High Severity:

If we have a typical scenario in which the application get crashed, but that scenario exists rarely.

- Low Priority and Low Severity:

There is a mistake like "You have registered success" instead of successfully, success is written.

Testing an executable application for portability across system platforms and environments, usually for conformation to an ABI specification.

Regression test cases are also based on the requirement documents. They are written more into detail and with every release (build), the testers need to do regression testing. The criteria for regression testing are; there should be no major defects while we do our smoke test and functional testing.

Security/penetration testing is testing how well the system is protected against unauthorized internal or external access, or willful damage. This type of testing usually requires sophisticated testing techniques.

In GUI testing, need to cover the customer requirement if don't have to validate  Font size, colors, spellings(labels) etc.

Every application should follow Microsoft rules like

- Controls should be Initcap (i.e every label should start with Capital letter )Can observe that in Win applications every label starts with Caps

- OK or Cancel button should exist

- Controls should not be overlapped

- Controls should be alligned properly (left side alignment is mandatory but the right side is optional)

- Controls should be visible

- Short cut keys should be provided

- System menu should exist (i.e if u press Alt key + Space bar a menu will appear at the left most corner )

- Mouse pointer events 

Colors, Label Names, Tab Order, Alignment, graphs , Navigation of the software to test in GUI Testing.