Saturday, 28 January 2012

Quality Center




Quality Center


Quality Center is an enterprise-wide application that is based on Java 2, Enterprise Edition (J2EE)technology.
Quality Center streamlines the quality management process —from requirements gathering through planning, scheduling and running tests, to defect/issue tracking and management —in a single browser-based application.
Quality Center Login Page is shown below
 


Thursday, 26 January 2012

Real time scenario questions


1.What could be the possible tests for testing a web page which displays flag of a country n some text in their language(for example Arabic ) when a button called Arabic is pressed and displays flag of another country and some text in English when a button called English is pressed?(internationalization)?
Ans) Button Pressed in Arabic:

1. Flag for the appropriate country with matching Text Displayed.

2. Correct Flag displayed, Text Wrong.

3. Correct Text, Flag wrong

4. Flag wrong, Text wrong

5. Null, Null

6. Correct Flag, Null (Text)

7. Creect Text, Null (Flag)
2) How do you complete the testing when you have a time constraint?
we need to check that the application is being tested for the first time or its a updated version.

Tuesday, 24 January 2012

Software Quality Assurance Life Cycle

In this article we have tried to map a Software Quality Assurance Life Cycle or Software QA Life cycle with a the normak SDLC.
 Also for each phase of SDLC the SQA activities are identified:

1. Software Concept and Initiation Phase

SQA should be involved in writing and reviewing the Management Plan
to ensure that processes, procedures and standards identified in the

Sample Bug report

Bug Name: Application crash on clicking the SAVE button while creating a new user.
Bug ID: (It will be automatically created by the BUG Tracking tool once you save this bug)
Area Path: USERS menu > New Users
Build Number: Version Number 5.0.1
Severity: HIGH (High/Medium/Low) or 1
Priority: HIGH (High/Medium/Low) or 1
Assigned to: Developer-X

Web Security Testing Checklist

1. Try to directly access bookmarked web page without login to the system. 
2. Do not sign-on system, directly try to download the file from the available download url, such as the inputhttp://url/download?name=file and check if the systems restrict you to download the file. 
3. sign out and then press the Back button to access the page accessed before. 
4. ID / password authentication method: check with valid and invalid passwords, password rules say cannot be less than 6 charecters, user id and password cannot be the same etc.

Sunday, 22 January 2012

Test case Defination,Example


Test Case Definition, Template, Example, Tips
DEFINITION
A test case is a set of conditions or variables under which a tester will determine whether a system under test satisfies requirements or works correctly.
The process of developing test cases can also help find problems in the requirements or design of an application.
TEST CASE TEMPLATE
A test case can have the following elements. Note, however, that normally a test management tool is

100 Types of Testing Definations


1. Acceptance Testing: Formal testing conducted to determine whether or not a system satisfies its acceptance criteria and to enable the customer to determine whether or not to accept the system. It is usually performed by the customer.
2. Accessibility Testing: Type of testing which determines the usability of a product to the people having disabilities (deaf, blind, mentally disabled etc). The evaluation process is conducted by persons having disabilities.
3. Active Testing: Type of testing consisting in introducing test data and analyzing the execution results. It is usually conducted by the testing teams.
4. Agile Testing: Software testing practice that follows the principles of the agile

How to write good testcases and Bug reporting

To develop bug free software application, writing good test cases is essential.

Here, we will see how to write good test cases.

Before seeing this, we should understand what is Good Test Case.

There won't be any solid definition for "Good Test Case". 

I will consider a Test Case as "Good" only when a Tester feels happy to follow the steps in the Test Case which is written by another Tester.