Scribd
Upload
73 views

Case Study

The document is a test plan for testing a new web-based system being developed by AltraTalk, a leading mobile service provider in Asia Pacific. The test plan outlines the scope of testing, which will include smoke testing, installation testing, and functional testing to verify system functionality and address issues. It defines test deliverables and schedules, identifies risks, and describes the test team roles and environment needed to execute the testing.

Uploaded by

Homework Ping
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
73 views

Case Study

The document is a test plan for testing a new web-based system being developed by AltraTalk, a leading mobile service provider in Asia Pacific. The test plan outlines the scope of testing, which will include smoke testing, installation testing, and functional testing to verify system functionality and address issues. It defines test deliverables and schedules, identifies risks, and describes the test team roles and environment needed to execute the testing.

Uploaded by

Homework Ping
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 9

Research Paper help

https://www.homeworkping.com/

ECX5267
Software Testing and Quality Assurance
Case Study

Name

: S.W.B.P.Kumara

Registration No

: 40566279

Submit Date

: 15-01-2011

Center

: Colombo

Question 1
1. INTRODUCTION
AltraTalk is a leading mobile service provider in Asia pacific. AltraTalk
currently has an in built computerized system to manage their day to day activities in
terms of
Connection Management
Billing
Payments
They wanted to develop a system that would help them coordinate their day to day
activities as well as take feedbacks from their internationally placed clients, with ease.
1.1. PURPOSE
AltraTalk IT management has decided to create a new web based system which can be
accessed by all the users via internet and intranet.

1.2. OVERVIEW
This is a QA test plan to test the AltraTalk web based system in order to verify the
system functionality and addressed issues. Emphasis on following:
Testing Objectives
Identified Risks and Mitigations
Testing Scope
Testing Types
Test Approach
Testing Schedule
1.3. DEFINITIONS, ACRONYMS AND ABBREVIATIONS
IT Information Technology
2

QA Quality Assurance
VB Visual Basic
OS Operating System
SQL Structured Query Language
2. SCOPE OF TESTING
2.1. PRODUCT OVERVIEW
The current system is a VB based windows client and found to have causing following
concerns
a. Due to expansion of the business different branches were open in different
geographical locations and the system need to be able to accessed from anywhere in
the world
b. Look and feel nature of the screens to be more appealing and is not restricted to tool
specific screen
c. Technology trend should move with proven good technologies that are scalable
where system is able to change with the evolving business
AltraTalk required a platform to support the companys business development
strategy of supplying additional mobile services to end users. This approach
demanded a sophisticated billing system capable of handling the complex
accounting processes between the AltraTalk operator and its partners.

2.2. PRODUCT RISKS


a. Product must contain in different language, because different countries and different
community use different languages.
b. Web base system works with multiple OS versions [Windows XP SP3, Windows
Vista 64, Windows 7 (32 and 64 bit)
c. System works with multiple browser versions such as Internet Explorer 8, Firefox
3.5.6 will be supported
d. System which can be accessed by all the users via internet and intranet.

2.3. TEST COVERAGE


Smoke testing
a. A quick-and-dirty test that the major functions of a piece of software work.
Originated in the hardware testing practice of turning on a new piece of
hardware for the first time and considering it a success if it does not catch on
fire.

Installation Testing
a. Confirms that the application under test recovers from expected or unexpected
events without loss of data or functionality. Events can include shortage of disk
space, unexpected loss of communication, or power out conditions. If
installation fails then our program will not work on that system not only this but
can leave users system badly damaged. User might require reinstalling the full
operating system.

Functional Testing
a. Testing the features and operational behavior of a product to ensure they correspond
to its specifications.
4

b. Testing that ignores the internal mechanism of a system or component and focuses
solely on the outputs generated in response to selected inputs and execution
conditions.
c. Testing based on an analysis of the specification of a piece of software without
reference to its internal workings. The goal is to test how well the component
conforms to the published requirements for the component.
2.4. FUNCTIONAL REQUIREMENTS
Criticality Functional Requirement
High
Human resources
1. Tracks employee sick and personal time allowed versus time taken
2. Supports the tracking of individual employee date of hire and

anniversary dates
3. Supports printing of payroll checks
4. Supports the tracking of federal payroll tax processing
5. Supports the tracking multi-state and providence payroll tax

processing
6. Federal, state, and providence based payroll tax tables are included

with Software Sale and Post-Sale Updates Provided


7. Supports employee tax accruals and reports

Medium
Sales
1. Application must capture appropriate information and produce

trend analysis reports


2. Trend analysis by customer and product, including profitability by

customer
3. Monthly detail by customer and invoice
4. Sales analysis by state
5. Daily activity report

2.5. OUT OF SCOPE


Unit testing involves only those characteristics that are vital to the performance of the unit
under test. This encourages developers to modify the source code without immediate
concerns about how such changes might affect the functioning of other units or the program
as a whole.

3. ASSUMPTIONS
Number of different language must be 20.
Every geographical areas use our target OS versions and browser versions.
Internet coverage is in grand level.

4. TEST DELIVERABLES AND SCHEDULE


Every module successfully completes within 2 months and after that start testing.
Testing period must be 1 month for a module.

5. TESTING APPROACH
5.1. TESTING TYPE 1 (SMOKE TESTING)
5.1.1. Objective
The installation testing will validate that: after every module
5.1.2. Entry Criteria
Install (teller) machine in identified locations.
5.1.3. Exit Criteria

Smoke test is successfully completed.


5.1.4. Test Suspension and Resumption Criteria
Install all machines and test all of them.
5.2. TESTING TYPE 2 (SYSTEM TESTING)
5.2.1. Objective
System testing will validate after smoke testing
5.2.2. Entry Criteria
Install software and made connection
5.2.3. Exit Criteria
System testing is successfully completed
5.2.4. Test Suspension and Resumption Criteria
Test network and database connection
6. TEST TEAM
6.1. QA TEAM ORGANIZATION
1. Software Tester - Only executes manual test cases, possible creates them
2. Software Quality Analyst - works with Business Analysts to find testable
requirements, and creates test cases with the Software Tester
3. Software Quality Analyst Senior - more experienced version of above, gets to
manage both 2 and 1
4. Software Quality Analyst Lead - develops test plans for individual functional
modules
5. Software Quality Manager - manages QA resources to test functionality within
timeframe
6. Software Quality Architect - works with management to determine how much
time is needed for testing, what testing will cover, and reports metrics and issues
7. Software Quality Director - evaluates new tool purchases, determines when
training is needed, conference schedules, when everyone can eat lunch, go home,
and assigns restroom privleges
7. TEST ENVIRONMENT
7.1. SOFTWARE AND HARDWARE
7

OS versions

Linux (ubuntu 10.10)

Server versions

Linux enterprise server

Wireless Dongles
Modem + Router
Web hosting
Web server
Domain name
Personal computers
Server machines

Question 2
Test
Case
ID
C1

Feature
description

prerequisite
s

Want to
Permanentl
y disconnect
a mobile
connection
on request
but there is
pending call
charges

Nil

C2

Permanentl
y disconnect
a mobile
connection
on request

Cut off
officer id
And
cut off
date

Test
Description
(test steps)
1.system
request
consumer
mobile
number or
NIC
2.consumer
enter
mobile
number
3.display
account
4.if there
are pending
call charges

Input
data

Expected
result

Actual
result

Status
(pass/fail)

Defect
ID

Mobile
number

disconnect

Please pay
pending call
charges

fail

Pending
call charges

1.system
request
consumer
mobile
number or
NIC
2.consumer
enter
mobile
number
3.display
account
4.if there
are not
pending call
charges

Mobile
number

disconnect

disconnect

pass

Nil

C3

Permanentl
y disconnect
a mobile
connection
on request
but there is
pending call
charges in
some
accounts

Nil

1.system
request
consumer
mobile
number or
NIC
2.consumer
enter NIC
3.display all
accounts
4.if there
are pending
call charges

NIC

disconnect

Please pay
pending call
charges

fail

Pending
call charges

C$

Permanentl
y disconnect
a mobile
connection
on request

Cut off
officer id
And
cut off
date

1.system
request
consumer
mobile
number or
NIC
2.consumer
enter NIC
3.display all
accounts
4.if there
are not
pending call
charges

NIC

disconnect

Perm
Disconnected

pass

Nil

You might also like