Shinetech responsibilities: progress control, Test Cases Execution, Test Result and Bug Report delivery
Test Environment: Windows 2000 with Flash8/9, Windows XP with Flash 9,
Windows ME with Flash 8, Vista Business with Flash 9, Vista Ultimate
with Flash 9
Tools: Visual Studio Team System ( VSTS) for Requirement management,
Bug management, Task assignment, etc., Flash Player 8/9 , DevTrack for
Bug Management
The client
The
client is a leading public e-gaming software developer and supplier in
Canada who creates today's most innovative online casino, poker and
bingo gaming software for internationally recognized brands.
What the client wanted
The
client had lots of development work to implement, for focusing
resources on its core business, lowering the human cost, products' risk
and meanwhile, accelerating progress of testing work and enhancing
testing quality, the client divided the whole testing work in several
parts. One appointed team was responsible for studying the requirements
and designing the Test Case, one appointed team was responsible for
executing the Test Case and reporting the Test Result, and another
appointed team took responsibilities for checking and accepting the
Test Result and Bug.
Shinetech's responsibilities
were to execute the Test Cases based on understanding the whole system,
report the Test Results, Bugs and cooperate with developers to resolve
the problems and took Regression Test at the same time.
Challenges
The
project was very complicated because there were several systems to be
tested. We needed to acquaint ourselves with diverse client
application, due to the applications were based on various databases
like T-Server, Author-Server, Game Server and etc, we must find out how
these databases configured so that we could learn more about the whole
system and execute the testing work smoothly.
The
whole Test Cases were 40 thousand items, and there were more than one
hundred Excel documents, twenty Requirement documents or PCP (project
change request). It was necessary for us to learn position about the
corresponding knowledge to contribute to the process of executing the
Test Cases.
Our Solutions
Executed the Test Cases and recorded Test Results
By training provided by client, browsed the Requirement document, and
played the game which would be tested, we came to understand probable
operation flow of the application and formed some basic estimation
which parts should be follow closely when executed the Test Cases. And
then peruse the Test Cases sample to realize its style. Based on
understanding about the whole system which took us two weeks, we
started to execute the Test Cases and recorded the Result of every Test
Case if Pass, Fail, N/A or Skip. And also we made several favorable
comments about some essential Test Cases so that the Test Results would
be more clear and open-and-shut. For example, we would put
corresponding bug's ID and make some favorable comments about the Test
Case which was Fail. Meanwhile, we employed Excel to produce Pass
percentage of the Test Cases which contributed to specifically
functional module automatically and reported it to client as a Test
Result.
Although we were only responsible for Test Case Execution, we
communicated with the client continually to learn details of the whole
project, like something not included in the Test Cases or Test Cases
not be updated in time according to the PCR ( project change request).
Reported the Test Results
According to the Results of executing the Test Cases, we generated a
Results Report with our analysis for client's reference. Meanwhile, we
made periodical statistics of the Test Results for every tester in a
period of time, like the number of Test Cases executed, Pass percentage
of the Test Cases, quantity and quality of the Bugs ( if it is a real
bug, if described clearly and roundly, if cause misunderstanding easily
) and subsequently produced the periodical evaluation of every tester.
Due to this kind of evaluation, the client would have a clear view of
our services. Also recurred to VSTS, the client could know the progress
of the project and see what the tester was doing at any time.
Submitted the Bugs
As mentioned, we placed great emphasis on quality of the Bugs. When
submitted the Bugs to client, we prescribed standard format to describe
the Bugs, and emphasized the description must be simple and
perspicuous, in the meantime we took full advantage of logs to make the
description could be more comprehensive, so that the developer could
understand the problems which be raised by tester easily. Also as an
important part of Bug Tracking, our tester communicated with developer
continually to assist the Bugs resolved as soon as possible. In the
process of Bug Tracking, in order to improve the efficiency of the
whole testing flow, we made an appointment with client that any
tester's Bugs should have feedback within two days.
Benefits
In virtue of our assistance client had focused resources on its core business.
Client had lowered the human cost and products' risk.
Testimonials
"I just wanted to report on the excellent work and leadership of the
Java team on their work for the project. The core application work is very
good and we are most pleased and amazed with their progress. "
