More Exams here…
Createobject(connectivity name)dbconnect(connectivity name) open(connectivity name)None of the above
Identifying test conditions only, not Identifying test casesNot Identifying test conditions, Identifying test cases only Identifying test conditions and Identifying test casesIdentifying test conditions or Identifying test cases
FileSystemObject.Getfolder()FileSystemObject.selectfolder() FileSystemObject.retrievefolder() FileSystemObject.openfolder()
makes test preparation easier.means inspections are not required.can prevent fault multiplication.will find all faults.
Reviews cannot be performed on user requirements specifications.Reviews are the least effective way of testing code.Reviews are unlikely to find faults in test plans.Reviews should be performed on specifications, code, and test plans.
test recording.test planning. test configuration.
linkage of customer requirements to version numbers.facilities to compare test results with expected results.the precise differences in versions of software component source code. restricted access to the source code library.
Boundary value analysisEquivalence partitioningDecision table testingState transition testing
Performance testingUnit testingBusiness scenariosStatic testing
Unit testingRegression testingAlpha testingIntegration testing
Define when to stop testingEnd of test levelWhen a set of tests has achieved a specific pre conditionAll of the above
Supplier issuesOrganization factorsTechnical issuesError-prone software delivered
Only Project risksOnly Product risksProject risks and Product risksProject risks or Product risks
Tools and techniquesProcedures and standardsProcesses and walkthroughsReviews and update
get Data (variable, dtGlobalSheet)get DataTable(variable, dtGlobalSheet) Set Data(variable, dtGlobalSheet)Set DataTable(variable, dtGlobalSheet)
To identify, evaluate, and rank tools, and recommend tools to managementTo determine what kind of tool is needed, then find it and buy itTo initiate the tool search and present a case to managementTo identify, evaluate and select the tools
SDLCProject Plan PolicyProcedure
ISO 1926ISO 829ISO 1012ISO 1028
Planning and controlTest closure activitiesAnalysis and design None.
Plan, Do, Check, Act Plan, Do, Correct, Act Plan, Debug, Check, ActPlan, Do, Check, Accept
System testingIntegration testingSmoke testingAcceptance testing
Decision testing Decision tablesEquivalence partition Transaction diagrams
Agile testingBeta testingBranch testingAd-hoc testing
Process flow modelMenu structure modelState transaction modelPlain language specification model
To measure the size of the functionality of an Information systemTo measure the functional requirements of the projectTo measure the functional flowTo measure the functional testing effort
Individual’s knowledgeUser manualThe existing system (For a bench mark)The code
Planning, Individual preparation, Kick off, ReworkPlanning, Review meeting, Rework, Kick offPlanning, Review meeting, Rework, Follow up Planning, Individual preparation, Follow up, Kick off
Mail (will not be published) (required)