Friday, February 15, 2008

Visual studio 2008 training kit tester's perspective



URL
XMLFILE

07 - The Testers Perspective.wmv 41ffa6c1-04b6-410c-a2a2-08bc38417168 -2.91131855 module 1.7154309 testers perspective 4.4612699 considering 6.08748985 value up 8.8090239 testing practices 12.1836735 vsts testing 14.40154315 features 16.27769395 principles 18.52788325 into practice 21.9672268 exactly what mean 26.1538345 testing objectives 29.43581975 unit testing 32.21739345 qa testing 35.24984245 value up testing principles 38.0939377 example 39.84278915 illustrates 42.529898 good tester 45.0026701 applies 46.65903745 principles 49.97120865 assess customer value 53.7819241 ultimate 55.78503515 objective 57.8751917 qa function 59.78200345 general 61.8776917 source confusion 64.25339915 exactly what 67.28636965 primary 70.37658625 testing objective 73.7221372 test function 77.6621248 advocate customer 80.8161384 customer value 83.53489005 tester there for 86.16321545 assess 87.97580505 value 90.47448305 unit testing 92.5674388 developers 95.1319003 also doing testing 98.5055556 development activities 102.41481415 quality of code 105.94859755 viewpoints 108.32082885 objectives 111.26153975 focus of module 114.4487109 tester responsibility 118.6961735 value of testing 121.22896605 principles 123.13545355 four core 125.2627064 key identity 128.79447285 important problem 131.542771 quickly 133.35675515 too long 134.98146945 drilling 139.07612135 entire system 142.2002676 quickly 145.0440193 focus on risk 148.63689345 focus and hone in 152.04389345 technically complex 155.2307574 edge case 156.9198266 bugs 161.61285605 testing effort 165.11022005 tests to drill into those 168.2637869 very nature 171.454127 complex aspects 174.7682393 focusing high risk areas 178.4860227 focus some risk 181.92480615 testing effort 185.144864 risk analysis 187.42684475 wrong 190.021059 identify 192.86519165 key risk areas 195.95941045 spread 197.92746605 across 200.33283225 maximizing 202.30238665 diversity 204.39648415 third principle 207.2400953 testing techniques 210.3672778 different 211.83438665 angles 213.710525 manual testing 216.0832495 conjunction 220.20840365 should be used 223.27512365 replace completely 226.49421775 suitable combination 230.5595624 different perspectives 233.5569955 conforms 235.2478719 requirements 239.18266335 test the resilience 242.52578575 break software 245.02409755 stress testing 248.2447937 security testing 251.8713561 different perspectives 255.56101365 techniques 258.30762025 overall successful 261.4653957 final principle 265.27922795 prescriptive 268.2490295 metric 269.3433538 measure 271.4058402 test effectiveness 275.0594513 number of bugs 280.03127785 thorough job 285.06324495 sloppy development practices 289.3765681 finding information 292.34658055 end of day 297.25440255 little example 299.34642865 scenario 301.47381525 Chris anna 305.501788 bug counts 309.5976565 more thorough jobs 314.50475175 Anna only found 74 319.31744565 subsystems 321.78580165 application 323.69360435 focused all 326.56813385 subsystem 1 329.0090375 long time 331.9134921 got all 333.79046945 severity 337.32134475 spent time 339.7237971 focusing on that 342.85213155 anna's result 347.9167155 50 in subsystem 1 351.57540595 certain amount of time 355.1984354 pretty sure 357.6690715 more bugs 360.7939332 other 364.57505445 6 bugs 366.41841275 across 370.0414649 all bugs 373.01414175 equal severity 375.4507064 reality 377.48399325 question 379.41949665 which testers 383.01580275 most thorough job 388.48669165 professional testers 391.76386625 as many bugs 395.4220386 actually 397.51864515 information produced 400.79838215 project manager 404.4549468 subsystem1 408.11171545 devote 410.36352385 effort 412.6744116 additional info 416.2384479 scrap subsystem1 421.32930505 redesign rethink 426.9569082 small proportion anna’s work 432.4584717 next project 435.0826236 value up principles 439.92730505 identified important problems fast 446.21124605 spread across 448.36551815 multiple 451.05328235 less concerned 454.9622132 prescriptive 459.430508 rest of team 462.3981395 ascertain 464.21378235 quality 468.8067234 as mentioned earlier 471.15382885 objective 474.0610284 customer value 476.7479581 questions 479.5296259 test team asking 483.091542 set of questions 485.8720783 assessing 487.9034626 proving 490.46512025 customer value 496.1862166 performance security ready 500.78045585 tested changes 503.53008845 one build to next 506.5926395 tests covering 510.96794905 new functionality 515.0319955 stale tests 517.6559683 new pieces of code 523.41000115 what has not been tested 527.0335794 code coverage 529.5349944 analysis 531.6271316 feedback 536.66369845 does it work in production 540.9428141 as well as in lab 543.8833969 test environment 546.9439547 mirrors 549.03819055 testing enough 552.65964855 completed 556.0053141 happy overall 560.94281185 when should we be running tests 565.53918145 throughout lifecycle 570.16394225 distinct places 573.25897965 enumerate 578.13445585 which test should we automate 582.4448651 when manual testing 586.0078923 efficient team 588.44801705 answer 590.9483266 questions 593.13645925 effectively 595.67068145 assess 597.51014745 customer value 600.23310205 ultimate objective 602.97929825 some tools 604.9186826 techniques 608.8550669 delivering 611.60657375 customer value 616.4177427 scenarios 619.7043549 primary statement 624.48256695 customer requirements 628.26352955 good scenario testing 632.7352438 new scenarios 635.23607605 evolve 637.426915 continue test 640.42601365 lifecycle 644.2057064 performed manually 648.5806622 automate scenario testing 652.2055114 vsts 655.5194989 record interaction 659.74016105 replay http level 663.8339252 user interface 667.92931975 web tests useful 671.49233905 code coverage 675.5870715 just small surface area 679.17901705 how effective 682.0233583 automated tests 685.27405445 reuse same tests 688.5252302 many times over 692.9006599 results intensive 695.49492745 complex 698.74608505 testing against 701.68459985 directly asses 704.21122685 manual testing 707.245991 good combination 711.3063402 answer question 716.21384815 delivering customer value 721.27955335 ensuring test completeness 725.77962365 answers to question 728.4971758 one hand 730.65427105 requirements 735.5001837 what code hasn’t been tested 739.6559774 check scenarios 743.53229145 code coverage 746.9701939 tests exercising 750.1902064 high proportion 754.379932 implement requirement 757.68930955 fault cases 761.00185945 exercise negative cases 764.723915 error handling 767.72300685 exception handling 771.7523674 we need to consider 776.37823135 multiple different angles 780.7860352 link work items 784.5688402 specific test cases 788.16453975 code coverage results 791.97616105 test coverage 795.8517722 surface 797.9134978 reports 800.5098674 vsts can produce 805.66552275 scenarios have and haven’t been tested 810.66610435 untested to passed 814.00963495 successive builds 817.0104241 precisely which 819.29115425 tested 820.6978946 passed 822.97842405 other metrics 825.6354728 code churn 829.7637325 effective from perspective 833.3251259 customer value 835.8270329 when to be testing 838.82439125 different points 841.54415765 lifecycle 845.6400545 unit tests 849.2637404 part of check in 851.3261384 policy 852.8586996 enforce 854.95398645 daily builds 858.2978708 overnight build 862.2387744 build verification tests 866.48545015 all code checked in 871.0496724 how good build 873.2977404 name build 875.2690896 pass over 877.5194513 testing 879.61398985 release build 881.6457166 customers 885.1432665 criteria testing 888.2709513 final qa checks 892.4890193 looking good 897.5516735 qos testing 901.92707035 captured early on 905.42904085 delivered supported 908.959974 how well software 911.30598645 perform 914.21095805 load stress performance 918.7727858 conditions degrade 922.68231295 vsts help 925.83785265 load testing 929.36736625 exposed 931.65207715 team suite 934.46280845 tester edition 937.52759415 security testing 940.90277785 certain aspects 945.08997625 certain attack vectors 949.2782506 security testing 952.74895695 special discipline 956.37228465 good threat analysis 960.1542472 randomly throwing 966.37193995 context application deployed 970.2501259 key threats 972.93815875 vulnerabilities 976.09958735 specifically 977.90594225 hone in 979.25187875 vsts 981.1251463 provide tools 985.0315488 code analysis tools 989.3141293 potential vulnerabilities 993.1926259 integrate 996.3466418 third parties 999.7548243 rely on 1002.84746945 good threat model 1006.90856015 deployed 1009.78610095 conclusion 1012.50509415 key question 1015.41282315 test function 1018.13223365 is customer value 1021.00791955 being delivered 1023.8183493 answering 1026.19722905 able to answer 1029.822203 quality of service 1035.9799071 what tests should be run 1040.57116895 which tests automated 1049.1967506 demo look at 1051.3221361 web testing 1053.3573912 vsts 1055.88628235 take test 1058.3576996 associate 1060.6394479 work item 1062.7294139 test results 1065.3577665 associate those 1067.41978235 build 1070.29404995 test passing failing 1073.7003685 test fails 1076.60831295 create new bug work items 1079.9517359 results of tests 1084.0787359 creating new web test 1087.26518485 new test 1089.36107825 click ok 1092.1734683 accept default name 1096.2380023 creating web test for me 1099.29914745 warning 1101.17451365 enhanced 1107.6136202 web application 1111.1132155 test again 1114.33535265 msdn website 1118.9291304 msdn.com 1122.3314876 display explorer bar 1125.6151894 web test recorder 1128.4603039 navigating 1130.7737676 interacting 1134.0223561 http interaction captured 1137.2395919 recorded 1139.68198075 played back 1142.9594683 test rerun 1145.6189354 http requests 1148.2126168 home there 1150.49435945 complete 1152.55502955 click stop 1156.36890595 automatically 1158.71647625 run test first time 1161.86936515 associate test 1165.59023365 particular scenario 1169.15344565 test menu 1171.46592295 test view window 1175.15269505 properties 1177.840135 work items 1179.7476157 browse 1180.87164515 add 1183.27932205 scenarios list 1188.65518485 scenario browse msdn 1194.31107375 web test scenario 1197.03251815 click ok 1199.5010295 association 1202.1855556 test results 1204.31504315 publish 1207.16228125 results test 1210.18844675 build 1213.50000685 related set of builds 1217.74985605 period of time 1220.0951463 fails 1222.25242865 also point 1225.44061115 add new work item 1227.7548674 type bug 1230.784059 add work item 1233.09776875 type bug 1237.72550685 msdn web test failure 1241.00615765 nice thing 1242.7874184 when you add 1245.19474265 results of test 1248.3807098 file attachment 1251.4464275 bug pulled 1253.47489685 developer 1255.38361345 looking 1257.1622971 test results 625.8166372 all happened automatically

No comments: