Best Practices

 

 T  Testing esting Pr Process ocess sohuld sohuld be defned properly properly

 T  Testing esting pr process ocess can be smootened by testing tools

backedn version maintence must be done or exes backedn version maintence must be done or exes and version outlin out line ep pit itall all points points,, as as what what what what must must neve neverr be be allo allowed wed thro thro

spcifcation o values that are visible in all windows test scenario must be provided testing testi ng and and deplo deployment yment must aid entire entire team team with with client client there there testing stages must be distributed amongst team members testing testi ng must must be be risk risk based. based. Ie,e testing testing o o critica criticall things things frst th

provide clients reuirement and expectation rom exe under te chec heck li list mu must be be m ma ade o or tth he sa same i pos possible ible a ch checkl ecklis istt so so specify test environment create a demo point list

developers must write testing points beore relasing exe larger the testing team aster the relase always provide server, client pairs or testing, with working ol smoke testing positive testing negative testing rational testing perormance perorman ce testing "utomated testing test deects must be replied with video or image

 

col col col col col col col col col col

aggregate details

 

#utline the things that need to be tested $peciy what is expected rom testing, as to what must happpen and what must n repeated processes processes as exe exe replacement, replacement, archive archive recreation, recreation, older cleanup cleanup must b setups must be shortened % &an there be ' setup or uniue id,sim, ser, cli % delaer mapping or demo must be automated  

names and version changes gh beore releasing any exe say set o fles must not pass set o events must never happen set o fles ()$T be present

 

pdb, sln so crash on lo consec, pa

ormula o what values is shown y reducing their eorts  

en other things

   

frst enlist all testing cases small and large set test priority or seuence then separate test cases with respect to risk and usage name each test case block whenever new exe is to be tested then sir will tell which block needs to be tested st tware tware or versions versions list as checks checks in rows rows and versions versions in columns columns where where user can ! os, bcast type etc create a demo point list also, whenever a new eature is coded, it*s uncitonality demo de mo poin points ts must must be cate catego gori rise sed d and and al also so sepa separa rate ted d as as to to wha whatt poi point nts s mus mus tbe tbe c

ers create test cases with all +#$ then check it arrange by priotrity test in way in which it was designed invalid testing, do what developer did not expect proper mathematical testing test perormance with number o logins, algos uick release, time saving o tester, reliability identiy testing which can be automated

 

no test case name o reuirement or eature whith which it is associated allowance o no pass can be allowed, cannot be allowedpassno pass observation to test or not attach image /eect Priority /eect $everity

name o ssotware version o server , cli, sim os o testing tested by released by reuirements to be tested

0I1 "$"P, &rash, ma!

 

 

t

 

e autpmated

 

urce code gin, etc rticipant

   

 

st tick

   

ust be neterd into the demo sheet so when demo is given or the same then it is eplai vered in the demo, as dierent clients have dierent reuiremnets

 

   

I1 $##n, 0I1 I0 TI(2 or bug, workaround, trivial bug

 

 

ed

 

$pecifc 0low must be specifed or algo design proper setups or all sortware must be vailable version control tips

commenting best practices

check i someone else understands the code % encapsuali3e work 4ow o action

solve minimal issues

 

$pecifc places where each change must be made or implementation o a new algo

do not merge modules which cannot be merged. enable proper verison control source code olders i possible server, client pairs to be kept together. source code olders must contain the unctions or changes made changes and source code documentation must be done respectively to fnd code aster chan ch ange ges s mus mustt be be ma made de with with the the late latest st ex exe e and and mer merged ged wit with h a fna fnall vers versio ion n whi which ch can can be be up ensure that the code is more readable comments ensure code is pu33ling comments must be short code must be clear meaning ule variable and constant names

make blocks o dierent sections o sotware in diagram what 4ow does trade make what 4ow does a survelliance make what is broadcast 4ow etcetera fnding passwords rom login fle cleaning olders

 

 

odated at all client ends

must be provided