InterSystems test automation

398
-1

Published on

Steve Brunner, Director of Quality Development at InterSystems presented at MassTLC's automated testing event on June 12, 2013 at Brightcove, Boston, MA

Published in: Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
398
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
0
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

InterSystems test automation

  1. 1. InterSystems TestAutomationSteve BrunnerDirector of Quality Development
  2. 2. • Application Development Tools• Caché – Fast Scalable Secure DB• Ensemble – Integration Engine• DeepSee – Integrated Business Intelligence• iKnow – Unstructured Data Analysis Tools• HealthCare Applications• TrakCare – Electronic Patient Administration• HealthShare – Aggregated Electronic Health Record• Patient Master Index, Clinical Viewer, Active AnalyticsInterSystems Products
  3. 3. • 1300 Employees in 6 continents• Quality Development• Independent of Product Development• 60 people worldwide• Mixture of Automated, Semi-automated, Manualtesting of all productsInterSystems
  4. 4. • Unit Tests• %UnitTest is built into Caché• ~80,000 unique unit tests• ~47 Million executions in 2012 on 45 platforms• Continuous Integration Testing - KingTut• Build, Install, AutoTest every 2 hours with latest code• If FAIL, nag all who checked things in since last PASS• GUI Automation with HP Quick Test Pro• We author tests using inhouse developed Framework.Automated Testing
  5. 5. • Not free, not even cheap• Automation takes time and people and machines• Pick a budget, e.g. 15% automation, 85% manual• Prioritize – can’t do everything• Not enough time to write them or to execute them• Do risk assessment to pick areas to automate, basedon importance, detectability, code author, or history.• Semi-automation is OK, don’t force it.• E.G. verifying visual details like “Button turns Green.”Lessons:
  6. 6. • Best for trying permutations• May need to glue things together• Build, install, test. Lather, rinse, repeat.• You need to pay attention to failures• We developed our own tool for visualizing and trackingtest results.Lessons:
  7. 7. • Unit Tests best written by original developer• But often aren’t• Make tests runnable by the developers• Making them easy to run is important• We switched from a 3rd party tool about 6 years ago toan inhouse developed Unit Testing tool (%UnitTest).Lessons

×