Date post: | 11-Feb-2017 |
Category: |
Software |
Upload: | original-software |
View: | 771 times |
Download: | 0 times |
Quick Poll
What do you see as the main market drivers for improving your software quality process? (Tick all that apply)
1. Need for increased business agility2. Increased complexity in IT
environments3. Need for increased competitive
advantage4. Increased business risks5. Changing market requirements
AQM Challenges
Quality as a business imperativeAgility is a business imperativeDisparate teams
DepartmentalSkill gapsOff shoring
Access to informationProject statusReporting
Manual nature of testingAutomation is hard
Theatre of Operations
High profile, key systemsRequired rapidlyIncreasing complexityPressure on resourcesPressure on timescalesCommercial competitionIT competition
Quick Poll
Do you currently use a test automation solution to help you with your QA process?
1. Yes – high degree of automation2. Yes – partially successful3. Used to – not maintained4. Tried – was not appropriate5. Mostly manual
Part of the Problem or Solution?
Scripting code drivenHigh maintenance burdenLimited audienceTechnical specialists
Often shelf-wareSub Main
Dim Result(50) As IntegerDim i as IntegerDim NewResult as StringStartBrowser "http://pandora.ple.blahblah.co.uk/action.pega?f1000=SIGNON&profile=test3", "WindowTag=WEBBrowser"
Window SetContext, "WindowTag=WEBBrowser", ""Window WMaximize, "", ""
delayfor 3000Browser SetFrame,"Type=HTMLFrame;HTMLId=__pegMainFrame",""Browser NewPage,"HTMLTitle=PANDORA - TEST1",""
Result(1) = EditBoxVP (CompareProperties, "Type=EditBox;Name=f5p1", "VP=Object Properties;Wait=2,30")Result(2) = EditBoxVP (CompareProperties, "Type=EditBox;Name=f6p1", "VP=Object Properties2;Wait=2,30")Result(3) = EditBoxVP (CompareProperties, "Type=EditBox;Name=f8p1", "VP=Object Properties3;Wait=2,30")Result(4) = EditBoxVP (CompareProperties, "Type=EditBox;Name=f9p1", "VP=Object Properties4;Wait=2,30")Result(5) = PushButtonVP (CompareProperties, "Type=PushButton;Name=@ACTION=|ENTR", "VP=Object Properties5;Wait=2,30")Result(6) = PushButtonVP (CompareProperties, "Type=PushButton;Name=@ACTION=|APPR", "VP=Object Properties6;Wait=2,30")Result(7) = PushButtonVP (CompareProperties, "Type=PushButton;Name=@ACTION=|BACK", "VP=Object Properties7;Wait=2,30")
For i = 1 to 3Select Case i
Case 1 InputKeys "robir"PushButton Click, "Type=PushButton;Name=@ACTION=|ENTR"
Why Manual Testing?
AddressesUnit testingSystem testingRegression testingUAT
Performed byProfessional TestersSME’sBA’sEnd-users
Inadequately documentedOften the “Wild West”
Why Automation?
Manual testing is slowFaster feedbackConsistencyEmpower testersConfidenceDocumentation
Why Test AutomationMay Fail
Extensive ramp-up timeLower on-going value
Skills Acquisition
Build Script Library
Automation partially available
Script Maintenance Cycles
Benefit ‘Black-outs’Shelf-ware Warning
Benefit
Effort
Time
Eff
ort
4-8+ months
Programmatic Test Tools
Falling Back to Manual Testing
Less challengingMore effort
Skills Acquisition
Build Script Library
Automation partially available
Script Maintenance Cycles
Benefit ‘Black-outs’Shelf-ware Warning Benefit
Effort
Time
Eff
ort
4-8+ months
Programmatic Test Tools
Fall Back to Manual Testing
The Journey (Back) Into Automation
Manual testing is a good source forRequirementsHistorical risk assessmentBoundary conditions
Defect RecordsOften most detailedImportant automation test casesBut small percentage of test suite goal
Jump Start Your Automation
Build “automatable” test assetsDynamic manual testing
DocumentFasterCategorizeCollaborateDo onceAd-hoc or Scripted
Move Into Automation
Categorize manual test casesConvert to Automation
Automatically
Enhance withVariable dataValidation rulesData analysis
Maintain test casesDeal with constant changeSelf-healing
Success in Automation
No need for technical specialistsAbility to adapt to changeRapid process
Not another bottleneckTo run in parallel with manual testing