《cest培训手册parasoftctesttraingpresentationtempla课件》由会员分享，可在线阅读，更多相关《cest培训手册parasoftctesttraingpresentationtempla课件（105页珍藏版）》请在金锄头文库上搜索。
1、Parasoft C+test TrainingCathy FanSeptember 24, 2012AgendaPart 1Parasoft Test OverviewProject SetupTerminologyImportBDFStatic AnalysisTerminologyWorkflowTestingSuppressions ViolationsBest PracticesPart 2Automated Peer Code ReviewOverviewPre-commit vs. Post-commitAuthors, Reviewers, ObserversWorkflows
2、Auditing the Code Review Processcest培培训训手册手册parasoftctesttraingpresentationtemplaAgendaPart 3Unit TestConcepts and StrategiesGenerating Unit TestsStubs and Project ScopeAssertionsCoveragePart 4Advanced Topics on Unit TestStubsFactory FunctionsParameterizationRuntime Error DetectionApplication Monito
3、ringRuntime Error Detectioncest培培训训手册手册parasoftctesttraingpresentationtemplaParasoft Test OverviewPurpose: Defect preventionTask management and distribution (Supports all aspects of project management)The primary question isDo you have the ability to apply these technologies uniformly as part of a p
4、rocess and get results?NOT do you have access to these technologies?The key to effective usage is uniform application with minimal impact on the developers workflowParasoft Proprietary and Confidentialcest培培训训手册手册parasoftctesttraingpresentationtemplaParasoft Test Functionality OverviewStatic analysi
5、sAutomated peer code review (Language independent)Unit testingRuntime analysisCoverage analysisTask management and distribution (Supports all aspects of project management)cest培培训训手册手册parasoftctesttraingpresentationtemplaParasoft Proprietary and Confidential1Create code and/or Unit Tests (auto or ma
6、nual)3Execute nightly2Check into Source4Cross reference5Deliver results within IDEOverall Implementationcest培培训训手册手册parasoftctesttraingpresentationtemplaTogethernessSingle, uniform interfaceSame interface for all languagesSupport for all technologies needed in developmentWorkflow is naturalWork is t
7、ask-based and focused on resultsTHE KEY is uniform implementation in the groupIf implemented as a group practice, the result is huge productivity improvementsParasoft Proprietary and Confidentialcest培培训训手册手册parasoftctesttraingpresentationtemplaParasoft C+test Project SetupTerminologyEclipse Workspac
8、eDirectory path that you had to specify at startupContains a collection of projects Has a “.metadata/” folder and a “.cpptest” folderEclipse ProjectHas a “.project” filecest培培训训手册手册parasoftctesttraingpresentationtemplaProject SetupC+test needs to knowCompilerBuild commandsBuild optionsFilesMethodsIm
9、port project from embedded IDE Use existing build systemBuild data filecest培培训训手册手册parasoftctesttraingpresentationtemplaImporting a Projectcest培培训训手册手册parasoftctesttraingpresentationtemplaWhat is a BDFBDF gives this information to C+testText deconstructed build options- cpptesttrace v.9.4.0.10 -work
10、ing_dir=C:UserscfanATMproject_name=ATMarg=C:cygwinbing+.exearg=-garg=-Iincludearg=-oarg=obj/ATM.oarg=-carg=ATM.cxxcest培培训训手册手册parasoftctesttraingpresentationtemplaGenerating a BDFPrerequisiteThe project is buildable on the machinecpptesttraceMonitors the build and puts all commands into the BDFThe p
11、roject needs to be buildableOptions -cpptesttraceProjectName-cpptesttraceOutputFileFor more options and explanationcpptesttrace -cpptesttraceHelpEx. cpptesttrace -cpptesttraceProjectName=ATM makecest培培训训手册手册parasoftctesttraingpresentationtemplaImporting a ProjectThen test with Static Analysiscest培培训
12、训手册手册parasoftctesttraingpresentationtemplaCustom Compilerscest培培训训手册手册parasoftctesttraingpresentationtemplaTroubleshootingIf trying import from existing IDE results in project incorrectly being brought inDelete the project from the workspace and try againTry the BDF import methodThe BDF import is mi
13、ssing files from the project/is skipping the Static Analysis testDouble-check the C+test project propertiesProject Properties Parasoft C+test Build SettingsDouble-check the BDF looks correctcest培培训训手册手册parasoftctesttraingpresentationtemplaC+test BasicsIts time for C+test BasicsChapter 1 Introduction
14、 to Parasoft C+test Chapter 2 Creating Projects Lessons 1-3, 5Exercises 1-5Chapter 3 Team Workflow Read throughParasoft Proprietary and Confidentialcest培培训训手册手册parasoftctesttraingpresentationtemplaParasoft C+test Static AnalysisWhat IS Static Analysis?Variety of methodsPeer Review / Manual Code Revi
15、ew / Code InspectionPattern-based code scannersFlow-based code scannersMetrics code scannersCompiler / build outputBenefitsPrevent ProblemsTarget ProblemsLearningParasoft Proprietary and Confidentialcest培培训训手册手册parasoftctesttraingpresentationtemplaStatic AnalysisPattern-BasedFlow-BasedMetricsDefects
16、cest培培训训手册手册parasoftctesttraingpresentationtemplaWhat is: Pattern-Based SAWhat:Identify specific patterns in the codeWhy:Find dangerous practicesPrevents defectsEnsure inclusion of required itemsSecurityBrandingParasoft Proprietary and Confidentialcest培培训训手册手册parasoftctesttraingpresentationtemplaPat
17、tern-Based Static AnalysisQuick scan to list possible problemsFixing violations prevents certain classes of errorsEach source analyzed separatelyStatic analysis categories include:Logical ErrorsAPI MisuseTypographical ErrorsSecurityThreads and SynchronizationPerformance and OptimizationParasoft Prop
18、rietary and Confidentialcest培培训训手册手册parasoftctesttraingpresentationtemplaWhat is: Data Flow AnalysisWhat:Simulate execution to find patternsWhy:Find real bugsParasoft Proprietary and Confidentialcest培培训训手册手册parasoftctesttraingpresentationtemplaData Flow AnalysisSimulate hypothetical execution pathsD
19、etect possible errors along those pathsData flow analysis error categories include:ExceptionsOptimizationResource LeaksAPI misuseSecurityParasoft Proprietary and Confidentialcest培培训训手册手册parasoftctesttraingpresentationtemplaWhat is: Code MetricsWhat:Measurement of code based on various statisticsWhy:
20、Understanding codePossible problemsParasoft Proprietary and Confidentialcest培培训训手册手册parasoftctesttraingpresentationtemplaC+test Static AnalysisIts time for C+test Static Analysis Chapter 4 Static Code Analysis Lesson 1 - 9Exercise 1-6Parasoft Proprietary and Confidentialcest培培训训手册手册parasoftctesttrai
21、ngpresentationtemplaBeing SuccessfulChoose rules carefullyImplement progressivelyFewer to more rulesExtend date backwardSuppressions for exceptionsParasoft Proprietary and ConfidentialQUALITYQUALITYCode Review and Regression Testingcest培培训训手册手册parasoftctesttraingpresentationtemplaTips for Configurat
22、ionDont get overwhelmed!Same set of rules for everyoneSmall set of rules to have a valueFewer rules that are followed is better than more that are notIf you wouldnt fix it, dont check for itParasoft Proprietary and Confidentialcest培培训训手册手册parasoftctesttraingpresentationtemplaConfiguration OptionsCon
23、figuration affects adoptionRules for new code vs legacy codeCut-off datesAvoid “we want to comply with this later”Parasoft Proprietary and Confidentialcest培培训训手册手册parasoftctesttraingpresentationtemplaTackling Static Analysis OutputAvoid the old “automated build and email” modelAssign to last person
24、to touch the codeSend relevant tasks directly to developer UIParasoft Proprietary and Confidentialcest培培训训手册手册parasoftctesttraingpresentationtemplaSample UIParasoft Proprietary and Confidential1Results delivered as uniform view within IDE2Directly access line of code to fix3Check-incest培培训训手册手册paras
25、oftctesttraingpresentationtemplaStatic Analysis WorkflowSCMSource ControlcodeTeam ServerTest ResultsScheduled TestServerReport CenterCommand Line ExecutionTeam CodingStandardsDeveloperMachinesArchitect / Technical leadTestResultsProgram ManagerArchitectcest培培训训手册手册parasoftctesttraingpresentationtemp
26、laEase of use / FeaturesDuplicate/child test configurationsModifying test configurationsPrintable rule docsFavorites (personal and team)DifferenceSeverity ChangeScopingReportsRecommended quality taskscest培培训训手册手册parasoftctesttraingpresentationtemplaAddressing ViolationsUnderstanding code and violati
27、onSee rule documentation for rule detailsMultiple methods:Fix the codeSuppress exception to the rulesvia Team Servervia Code CommentsPeer reviewShould you re-test from your desktop?If you have time, code, and setup, sureData Flow analysis is time consumingParasoft Proprietary and Confidentialcest培培训
28、训手册手册parasoftctesttraingpresentationtemplaTroubleshootingSkipping filesCheck the C+test project settingsCheck that the mentioned in the BDFCompilation or Parse errorsDoes the project build outside of C+test?Check the C+test project settings/compiler being usedx86 and x84_64Make sure C+test is run un
29、der the correct environmentValidate the compilation errorCreate a Technical Support Archive with the preprocessed send it to support for helpcest培培训训手册手册parasoftctesttraingpresentationtemplaC+test Static Analysis 2Its time for C+test Static AnalysisChapter 5 Static Analysis Workflow Lesson 1 7, 9 12
30、Parasoft Proprietary and Confidentialcest培培训训手册手册parasoftctesttraingpresentationtemplaParasoft C+test TrainingCathy FanSept 25, 2012AgendaPart 1Parasoft Test OverviewProject SetupTerminologyImportBDFStatic AnalysisTerminologyWorkflowTestingSuppressions ViolationsBest PracticesPart 2Static Analysis R
31、eviewAutomated Peer Code ReviewOverviewPre-commitPost-commitWorkflowsAuditing the Code Review Processcest培培训训手册手册parasoftctesttraingpresentationtemplaStatic Analysis ReviewQuestions?cest培培训训手册手册parasoftctesttraingpresentationtemplaWhy do Code Review?Find defects earlyFind real functional problemsInc
32、rease breadth of understandingLeads to increased productivityParasoft Proprietary and Confidentialcest培培训训手册手册parasoftctesttraingpresentationtemplaMethods of Code ReviewCode Review “in a room”Wastes timeDevelopers are inhibitedUsing an automated infrastructureconsistentParasoft Proprietary and Confi
33、dentialcest培培训训手册手册parasoftctesttraingpresentationtemplaDetermining ReviewersWho reviews whomHow close are they in the code?Increase code understandingParasoft Proprietary and Confidentialcest培培训训手册手册parasoftctesttraingpresentationtemplaPutting it togetherTwo methods for code reviewPre-commitPost-co
34、mmitThe next slides show how to do itPlanningSetting up tasksPerforming the workFirst phase of code review should be pre-commitParasoft Proprietary and Confidentialcest培培训训手册手册parasoftctesttraingpresentationtemplaPre-Commit Code Review WorkflowParasoft Proprietary and Confidentialcest培培训训手册手册parasof
35、tctesttraingpresentationtemplaWhen to use pre-commitShouldnt be for normal experienced developersException: when first starting the Code Review processSetup policies to determine when to useNew developersNew team membersSignificant code changesMore than 2-3 files for a single fixParasoft Proprietary
36、 and Confidentialcest培培训训手册手册parasoftctesttraingpresentationtemplaWhen is it enough?When everyone agreesPre-commit will hold up other development effortsBalance between full review and getting things doneParasoft Proprietary and Confidentialcest培培训训手册手册parasoftctesttraingpresentationtemplaSetting Up
37、 Code Review from the UIPreferencesConcertoTeam ServerCode ReviewScope and AuthorshipSource ControlTest ConfigurationScopeCode ReviewCommoncest培培训训手册手册parasoftctesttraingpresentationtemplaPost-commit code reviewWho reviews whom is keyGuarantees that 100% of modified code is reviewed For experienced
38、developersUse for smaller changesParasoft Proprietary and Confidentialcest培培训训手册手册parasoftctesttraingpresentationtemplaCode Review HistoryConcerto stores everythingGreat for accountabilityWhat you sayParasoft Proprietary and Confidentialcest培培训训手册手册parasoftctesttraingpresentationtemplaReview Classif
39、icationsParasoft Proprietary and Confidentialcest培培训训手册手册parasoftctesttraingpresentationtemplaReading the Review GraphParasoft Proprietary and Confidentialcest培培训训手册手册parasoftctesttraingpresentationtemplaReview Task ClassificationNew issues by severityReviewer classifiesNew issues by categoryParasof
40、t Proprietary and Confidentialcest培培训训手册手册parasoftctesttraingpresentationtemplaReviewers TasksParasoft Proprietary and Confidentialcest培培训训手册手册parasoftctesttraingpresentationtemplaWhat shouldnt you look atCode formation use static analysisBeautificationNaming conventions Some are related to function
41、ality check thosePattern based should be checked in SAParasoft Proprietary and Confidentialcest培培训训手册手册parasoftctesttraingpresentationtemplaWhat should you look at?Metrics violationsThings not covered by static analysisFunctionalityExtend understanding of the codeParasoft Proprietary and Confidentia
42、lcest培培训训手册手册parasoftctesttraingpresentationtemplaThings to look forMake sure source control comments are meaningfultask ID is in the review comments so you know what the change is related toTry to understand what theyre trying to doWhat is the logicHow does it fit the overall systemHow “clean” is t
43、he codeProper design patterns MOST IMPORTANTDoes each class do one thingDoes each method do one thingAre methods named according to what they do?Naming should fitParasoft Proprietary and Confidentialcest培培训训手册手册parasoftctesttraingpresentationtemplaMore to look forRefactoringWhat is the general impac
44、t of the change being made?Do you know other areas the change will affect?Design patterns used are they appropriate?Other policiesParasoft Proprietary and Confidentialcest培培训训手册手册parasoftctesttraingpresentationtemplaReviewing code formattingNormally trust the SA tool to do thisNew developers doing p
45、re-commit get extra scrutinyLegacy code is a challengeContested policies are a challengeThey dont belong in early adoption, or even later.As people used to doing SA and CodeReview it becomes easier to introduce such changes.Parasoft Proprietary and Confidentialcest培培训训手册手册parasoftctesttraingpresenta
46、tiontemplaSetting HealthCheck PolicyParasoft Proprietary and Confidentialcest培培训训手册手册parasoftctesttraingpresentationtemplaThe Futurecest培培训训手册手册parasoftctesttraingpresentationtemplaParasoft C+test TrainingCathy FanSept 26, 2012AgendaPart 3Unit TestConcepts and StrategiesGenerating Unit TestsStubs an
47、d Project ScopeAssertionsCoveragePart 4Advanced Topics on Unit TestStubsFactory FunctionsParameterizationRuntime Error DetectionApplication MonitoringRuntime Error Detectioncest培培训训手册手册parasoftctesttraingpresentationtemplaCode Review QuestionsQuestions?cest培培训训手册手册parasoftctesttraingpresentationtemp
48、laWhat IS Unit Testing?Testing Units of CodeFunctional TestingAcceptance TestingSystem TestingRegression TestingCPPUnit extension“Code that exercises a small well-defined area of functionality to prove that it works as intended”Parasoft Proprietary and Confidentialcest培培训训手册手册parasoftctesttraingpres
49、entationtemplaWhy Unit Test?Regression TestingFinds unwanted changes earlierHelps validate designProduces better softwareDocuments current behaviorEasier to debug laterTest-Driven DevelopmentConfirms functionalityBecomes regression testsTime saved writing testsParasoft Proprietary and Confidentialce
50、st培培训训手册手册parasoftctesttraingpresentationtemplaKeep in mindUnit tests require a LOT of careUnit testing is a continuous operationTest suite maintenance is a commitmentNo silver bulletParasoft Proprietary and Confidentialcest培培训训手册手册parasoftctesttraingpresentationtemplaAnatomy of a Unit TestLike Blac
51、k-box testingSetupInput and global variablesMock functions (stubs), mock objects (factory functions), data sources, Call unitUsing the setupAssertionsValidate the outcome Expected vs. Actualcest培培训训手册手册parasoftctesttraingpresentationtemplaC+test Unit Test exampleAccount* getAccount(int num, string p
52、assword);void TestSuite_Bank_cxx_6ec01b54:test_getAccount_1()/ Setup function Inputs:Bank _cpptest_TestObject ;int _num = 0;:std:string _password = ;/ Calling the function:Account * _return = _cpptest_TestObject.getAccount(_num, _password);/ Assert valuesCPPTEST_ASSERT_EQUAL(0, ( _return );Parasoft
53、Proprietary and Confidentialcest培培训训手册手册parasoftctesttraingpresentationtemplaAssertions - What to assertEase of creating assertions leads to poor choicesAnything CAN be checked but should it be?Assertions should be connected to what youre trying to testAssertions should be time invariantCheck values
54、 by range, not equivalence“What do I expect here logically?”Bad AssertionsHow often do you WANT to manually verify an assertion?Daily or near-daily checking indicates poor assertion.Parasoft Proprietary and Confidentialcest培培训训手册手册parasoftctesttraingpresentationtemplaAssertions - Why assertions fail
55、Introduced coding errorFix the new codeFunctionality changedUpdate the assertionImproper assertionComment it out with a reason/ TODOParasoft Proprietary and Confidentialcest培培训训手册手册parasoftctesttraingpresentationtemplaUnit Test CreationAuto-GeneratedGood for freezing codeExposes exceptionsEasy to ab
56、useApply in targeted mannerBuilt-in Configuration: test optionsReplacing old unit testsTest cases per functionPrivate, protected, publicWizard-GeneratedSpecific scenarioHuman effortReview the tests as you work on the codeIts all the same to C+testcest培培训训手册手册parasoftctesttraingpresentationtemplaInpu
57、t ExceptionsReview and handleFix codeDrop assertionSkip testParasoft Proprietary and Confidentialcest培培训训手册手册parasoftctesttraingpresentationtemplaRun Unit Tests - ResultsBuilt-in configurations: optionsScopingResultsQuality TasksPost ConditionsAssertion FailuresExceptionscest培培训训手册手册parasoftctesttra
58、ingpresentationtemplaCoverageCoverageLineLine hit countDecisionPathSimple ConditionBlockStatementMC/DCcest培培训训手册手册parasoftctesttraingpresentationtemplaC+test Unit TestIts time for C+test Unit Test Chapter 6Lesson 1 8 Exercise 1 6 Parasoft Proprietary and Confidentialcest培培训训手册手册parasoftctesttraingpr
59、esentationtemplaWhere do tests live?Always under source controlSeparate auto-generation from hand-codedPossible locationsSame dir as class being testedSame structure, different dir, in the same projectSame structure, but separate testing projectTeam agreementParasoft Proprietary and Confidentialcest
60、培培训训手册手册parasoftctesttraingpresentationtemplaCreating and Maintaining Unit TestsWrite tests with the codeCreate the test when youre writing the codeHave a test for every task you completeIncreases understandingImprove assertionsMaintaining is more effort than creating. Dont create a test if you cant
61、 or dont plan to maintain it.Tests not run regularly become irrelevantMultiple strategiesUse automation for the frameworkUse templatesCreate everything by handNo silver bulletParasoft Proprietary and Confidentialcest培培训训手册手册parasoftctesttraingpresentationtemplaLegacy Test SuitesLeverage your existin
62、g suiteClean up incrementallySet policy based on current resultsTighten policy when in complianceParasoft Proprietary and Confidentialcest培培训训手册手册parasoftctesttraingpresentationtemplaExpanding and Customizing Unit TestsAuto-generated unit tests act as a good baseBorder values0, 1, -1, NULLFor more f
63、unctional and meaningful tests (Make your existing tests do more)Create unit test manuallyAdd logicExtend unit tests with a data sourceExtend unit tests with mock data (factory functions and stubs)Add test based on low-coverage areascest培培训训手册手册parasoftctesttraingpresentationtemplaExtending Coverage
64、Line coverage is just a starting pointDont be lured by 100% coverageCompletenessUse data sources, stubs, and factory functionscest培培训训手册手册parasoftctesttraingpresentationtemplaWays to fake dataStubs Replacement functionControl of testFactory Functions (Mock objects)Pre-initialized objects Control of
65、testParasoft Proprietary and Confidentialcest培培训训手册手册parasoftctesttraingpresentationtemplaStubsFuncA()FuncB()Scope of Testingcest培培训训手册手册parasoftctesttraingpresentationtemplaStubsFuncA()FuncB()Scope of Testingcest培培训训手册手册parasoftctesttraingpresentationtemplaStubsFuncA()FuncB()Scope of TestingStub_Fu
66、ncB()cest培培训训手册手册parasoftctesttraingpresentationtemplaStubsControl behavior of functionUsing stubs to direct flowIsolates the testFor consistent resultsStubs ViewCategoriesUserOriginalAutoUnlike unit tests, C+test caresParasoft Proprietary and Confidentialcest培培训训手册手册parasoftctesttraingpresentationt
67、emplaScopingProject ScopeUses all the symbols available in the projectSystem testingUses only the symbols available to the source testedStubs most likely neededIsolated testingcest培培训训手册手册parasoftctesttraingpresentationtemplaCreating and Using StubsCreating StubsTest Configuration for AutoStubs View
68、 for UserBoth distinguished by nameUsing StubsMake sure test configuration knows where stubs areUsed by defaultcest培培训训手册手册parasoftctesttraingpresentationtemplaParasoft C+test TrainingCathy FanSeptember 27, 2012AgendaPart 3Unit TestConcepts and StrategiesGenerating Unit TestsStubs and Project ScopeA
69、ssertionsCoveragePart 4Advanced Topics on Unit TestStubsFactory FunctionsParameterizationRuntime Error DetectionApplication MonitoringRuntime Error Detectioncest培培训训手册手册parasoftctesttraingpresentationtemplaQuestion?Question?cest培培训训手册手册parasoftctesttraingpresentationtemplaUnit TestingProject Setup f
70、or Unit TestingOne executable/library per C+test/Eclipse project default optionCreate separate test executable for each tested context CPPTEST_CONTEXT For smaller executablesRuntime Error Detectionruntime memory analysismemory leaks, null pointers, uninitialized memory, and buffer overflows Lightwei
71、ght instrumentationHas “rules”cest培培训训手册手册parasoftctesttraingpresentationtemplaStubs Cont.One “set” of stub per functionFunctionA() can have a user, safe, and auto stub all available in the same scope, but only one will be used.You CANNOT have two user stubs for FuntionA() for different behaviorsTes
72、t-case specific stub actionFunctions for Stubs Driven by Test Cases bool CppTest_IsCurrentTestCase(const char* id) cest培培训训手册手册parasoftctesttraingpresentationtemplaParameterizationUse data sourcesWhyEasier to maintainLess effort to extend testingOne unit test tests many conditionscest培培训训手册手册parasof
73、tctesttraingpresentationtemplaC+test Unit Test 2Its time for C+test Unit Test Chapter 7Lesson 5Exercise 2Parasoft Proprietary and Confidentialcest培培训训手册手册parasoftctesttraingpresentationtemplaWays to fake dataStubs Replacement functionControl of testFactory Functions (Mock objects)Pre-initialized obj
74、ects Control of testParasoft Proprietary and Confidentialcest培培训训手册手册parasoftctesttraingpresentationtemplaFactory FunctionsCreating objectMultiple versions of the same objectTests different states of your objectParasoft Proprietary and Confidentialcest培培训训手册手册parasoftctesttraingpresentationtemplaCre
75、ating and Using FactoriesCreating/SetupCreate header and source factory definitionsInclude header in tested source files (ffi CTRL+SPACE)In factory source file, define factory (ffs or ff CTRL+SPACE)UsingNot grabbed automatically like stubsNeeds to be written into unit testAutomatically by enabling “
76、Use factory function” in Test ConfigurationUse include from wizardManually writing it inRun unit tests as normalcest培培训训手册手册parasoftctesttraingpresentationtemplaExtending CoverageLine coverage is just a starting pointDont be lured by 100% coverageCompletenessUse data sources, stubs, and factory func
77、tionscest培培训训手册手册parasoftctesttraingpresentationtemplaC+test Unit Test 3Its time for C+test Unit Test Chapter 7Lessons 1 4, 6 11Exercises 1 4Parasoft Proprietary and Confidentialcest培培训训手册手册parasoftctesttraingpresentationtemplaApplication MonitoringBuilds and runs original executable with instrument
78、ationCoverageRuntime Error DetectionIdentify serious runtime defectsFor both developers and QASome limitation listed in Help Documentationcest培培训训手册手册parasoftctesttraingpresentationtemplaWrap UpProject ImportEmbedded, BDFStatic Analysis3 typesRunning and resultsThe only thing dev has to do? IMPORT!U
79、nit TestGeneration/ExecutionAdvanced topics (data sources, stubs, factories)CoverageApplication MonitoringProcess: scheduled and maintainedcest培培训训手册手册parasoftctesttraingpresentationtemplaParasoft Proprietary and Confidential1Create code and/or Unit Tests (auto or manual)3Execute nightly2Check into Source4Cross reference5Deliver results within IDEOverall Implementationcest培培训训手册手册parasoftctesttraingpresentationtemplaTraining Evaluationcest培培训训手册手册parasoftctesttraingpresentationtempla
