RE: [HELP] Ca'ch test chuong tri`nh phan mem

[Huy Q Nguyen <huynq@microsoft.com>]

Cha`o ba'c Hue^. va` ca'c ba'c

Nghe te^n ba'c quen quen kho^ng bie^'t to^i co' ddu+o+.c ha^n ha.nh bie^'t
ba'c ro^`i kho^ng nhi?\. Ho^m nay weekend ro^~i ra~i no'i la?m nha?m va`i
ca^u, co' gi` sai mong ca'c ba'c kha'c su+?a lu+ng cho ca'i\.

DDe^? gia?i quye^'t va^'n dde^` cu?a ba'c, co' le~ ba'c pha?i xem la.i ca'i
development process cu?a ba'c\. i't nha^'t ba'c pha?i ddi.nh nghi~a mo^.t
ca'i go.i la` Test Release Procedure trong ddo' khi mo^~i build ra ddo+`i,
i't nha^'t ta^'t ca? mo.i ngu+o+`i (development, testing, program
management) pha?i bie^'t ca'i gi` co' trong ca'i build mo+'i ddo', i't
nha^'t la` ca'i gi` kha'c so vo+'i ca'i build tru+o+'c\. To^i la^'y vi' du.:
bao nhie^u bugs fixed, bugs na`o (to^i assume la` ba'c co' tools dde^? keep
tracks of ma^'y ca'i na`y), the^m bao nhie^u feature mo+'i, va` ca'c fixes
cu?a development co' pha^`n na`o sensitive, co' the^? a?nh hu+o+?ng dde^'n
features na`o\. Ca'i document na`y co' the^? la` E-mail, web-page...

Trong Test Release Procedure cu~ng pha?i ddi.nh nghi~a ddu+o+.c mo^.t build
la` testable\. Kho^ng pha?i build na`o cu~ng testable\. Bba'c co' the^? co'
mo^.t build team rie^ng hoa(.c development la`m luo^n chuye^.n build (tuy`
project lo+'n hay nho?)\. Mo^.t build la` testable la` no' pass mo^.t so^'
quality criterias nha^'t ddi.nh\. Ca'c criteria na`y co' the^? do test team
vie^'t du+.a tre^n original specification\. Co' the^? quy ddi.nh la` chi?
co' testable build mo+'i co' the^? ddu+o+.c release ra testing cha(?ng
ha.n\.

To^i kho^ng la`m test nhu+ng to^i nghi~ la` ca'c chu+o+ng tri`nh test chi?
co' the^? giu'p ba'c co^ng ddoa.n na`y nghi~a la` no' co' the^? mo^ pho?ng
ca'c ti`nh huo^'ng (vie^'t ca'c test scripts) dde^? dda?m ba?o mo^.t feature
na`o ddo' pass its quality criteria (automated testing)\. Vi' du. ba'c co'
ca'i feature la` drop down menu thi` ba'c co' the^? vie^'t ca'i test-script
dde^? sao cho no' drop ca'i menu ro^`i click va`o mo^~i item cho no' ra ca'i
mo^.t ca'i dialog\. Ne^'u no' kho^ng pass thi` no' ba'o cho ba'c bie^'t\.
To^i no'i the^' kho^ng pha?i la` ca'i feature ddo' bugs-free dda^u nhe'\.
Khi ba'c co' test-script cho ca? 10 features ro^`i thi` khi ddu+a ra ca'i
build mo+'i, make sure no' testable ro^`i tester chi? ca^`n verify la.i bugs
ddu+o+.c fixed cho 10 ca'i features ddo', vie^'t test-scripts cho F11-Fn va`
test F11-Fn ma` tho^i\.

Sau khi xong he^'t ca? n features ro^`i thi` ba'c ba?o la` Code Complete,
ba^y gio+` la` giai ddoa.n integration hay la` stabilization\. Khi ddo' ba'c
pha?i test tu+` dda^`u la`m va`i vo`ng nhu+ va^.y (test passes)\. Sa('p
dde^'n khi ba'n SW ro^`i la` mo^~i bug fix la` pha?i co' ca^n nha('c, i't
nha^'t la` Program Manamement approve mo+'i ddu+o+.c...

DDa^y chi? la` mo^.t process to^i go'p y' va^.y\. Mo^~i co^ng ty, mo^~i
group co' khi la.i ddi.nh nghi~a rie^ng cho mi`nh mo^.t process rie^ng\.
DDe^? cho tha`nh co^ng thi` pha?i co' nhie^`u ye^'u to^' la('m kho^ng the^?
be^. ca'i na`y nguye^n xi qua ca'i kha'c ddu+o+.c, vi` co`n ra^'t nhie^`u
ye^'u to^' kha'c co' the^? la`m cho ca'i process cu+.c hay ddi tong nhu+
cho+i: budget constraint, schedule constraint, project to hay nho?...\. To'm
la.i la`m SW development nhu+ la` cho+i game, tru+o+'c khi cho+i ba'c pha?i
dda(.t ra rule of the game ro^`i mo+'i cho+i ddu+o+.c, ma` rule na`y qua
qua' tri`nh cho+i la.i pha?i su+?a tie^'p co+ ma`\. Ca'ch duy nha^'t la`
cu+' cho+i ddi ro^`i se~ co' kinh nghie^.m\. Co' gi` ca'c ba'c kha'c ke^?
the^m\.

Thank you
Huy Q. Nguyen


-----Original Message-----
From: HueDT [mailto:huedt@mailandnews.com]
Sent: Sat, October 16, 1999 3:30 AM
To: vnsa@list-server.net
Subject: [HELP] Ca'ch test chuong tri`nh phan mem


Cha`o ca'c ba'c,
Toi dang pha?i thu*.c hien test chuong tri`nh phan mem, co' ma^'y thac mac
muon ho?i ca'c ba'c nhu* sau:

Gia? su*? co' n feature can test, F1,... Fn (n>1)
Go.i ca'c Built la` Bi (i>1)


Gia? su*? Tester test B1 duoc 10 features , F1..F10 (trong qua' tri`nh test
co' bug), thi` co' B2. Va^.y tester ne^n:

 1. Vo*'i cac Feature tu*` 1..10 ma` co' lo^~i da~ duoc fix trong B2 thi`
test la.i vo*'i B2 + tiep tuc test cac features co`n lai ?

or
 2. Test la.i tu*` dau  ?

or
 3. Tiep tuc test ca'c feature F11..Fn  ?


Neu cho.n case 1, 3 thi` trong truong ho*.p na`o co' the^? bo? qua viec test
la.i toa`n bo^. ca'c feature khi da~ test du? 1 vo`ng cac feature ?
or
luo^n pha?i test la.i toa`n bo^. ca'c feature ne^'u co' nhieu built trong 1
vo`ng test cac feature ?


(Xet truogn hop trong thu*.c te^' la` viec fix bug cua feature Fi trong B1
co' the^? la`m cho feature Fj cha.y to^'t trong B1 la.i bi. lo^~i trong B2;
So^' feature lo*'n; )


To^i co' nghe no'i ve^` phan mem du`ng cho testing, vay day la` software
ho^~ tro*. trogn viec testing (bug report/fixing; ...) hay la` chi? du`ng
de^? kiem tra 1 loai SW na`o do' . That kho' co' the nghi~ la` co' 1 chuogn
tri`nh Test du`ng cho moi loai SW :))


Va` cuo^'i cu`ng la` ne^'u co' the^? duoc, ca'c ba'c co' the^? mo^ ta? giu'p
cach thuc hien 1 test ma` cty ba'c ap du.ng hay ba'c da~ tu*`ng ap du.ng ?

Ca?m o*n ca'c ba'c nhie^`u !
Hue.