API Strategy and Practice Conference
Hyatt Regency Chicago, 151 E Upper Wacker Dr, Chicago, IL 60601
REST APIs are key enabling technology for web services in the cloud. Mobile applications, service-oriented architecture, and the Internet of Things depend on reliable and usable REST APIs. Unlike browser, native, and mobile apps, REST APIs can only be tested with software that drives the APIs. Unlike developer-centric hand-coded unit testing, adequate testing of REST APIs is truly well-suited to advanced automated testing.
This brief talk will present a methodology for developing and testing REST API using a model-based automation.
Software Quality Association of Denver (SQuAD) monthly meet up.
To register, go to http://www.meetup.com/SQUADCO/
PPA Event Center, 2105 Decatur St, Denver, CO 80211 http://binged.it/1li0IXy
REST APIs are a key enabling technology for the cloud. Mobile applications, service-oriented architecture, and the Internet of Things depend on reliable and usable REST APIs. Unlike browser, native, and mobile apps, REST APIs can only be tested with software that drives the APIs. Unlike developer-centric hand-coded unit testing, adequate testing of REST APIs is truly well-suited to advanced automated testing.
As most web service applications are developed following an Agile process, effective testing must also avoid the "Testing Backblob," in which work to maintain hand-coded BDD-style test suites exceeds available time after a few iterations.
This talk will present a methodology for developing and testing REST API using a model-based automation and explain how this has the beneficial side-effect of shrinking the Testing Backblob.
ICST 2014 will be located at the Hyatt Regency Arcade in downtown Cleveland.
I will be attending ICST 2014 to kick off ICST 2016, of which I am the Co-Chair.
TEKsystems, 111 N. Canal Street 11th Floor, Chicago.
Here's a link to directions http://binged.it/1mrU2FZ
Rescheduled from Jan 28 to Feb 25 owing to very cold weather.
Acceptance Test Driven Development (ATDD) and Behavior Driven Development (BDD) are well-established Agile practices that rely on the knowledge and intuition of testers, product owners, and developers to identify and then translate statements into test suites. But the resulting test suites often cover only a small slice of happy-path behavior. And, as a BDD specification and its associated test code base grows over time, work to maintain it either crowds out new development and testing or, typically, is simply ignored. Either is high-risk. That’s how Agile teams get eaten by the testing BackBlob. This talk explains how model-based testing fights the backblob.
Open to Cerner staff.
This presentation explains how test models can drive development and defeat the testing backblob, instead of loosely stated behavior (BDD) or acceptance criteria (ATDD).
The meeting will be held at the University of Illinois at Chicago in rooms 1043-1047 of the Engineering Research Facility, 842 W. Taylor Street, Chicago, Illinois 60607.
This talk presents multi-dimensional testing, a model-based strategy to produce test suites that interleave non-trivial variation in system usage and load. Compared with equivalent but separate usage and load test suites, this achieves testing that is highly realistic and more likely to reveal catastrophic failure modes. A project in which this approach was evolved and used is described. An innovative model of system failure, the “dragon king” provides a useful model of failure modes in large reactive systems, providing insight into recent high profile failures of complex distributed systems. I argue that multi-dimensional testing is necessary to reveal dragon-kings.
WOPR20 was held in New York City on May 14-16, 2013, and was hosted by Liquidnet. Ross Collard was the Content Owner.
Loyola University Water Tower Campus (Chicago/Michigan Area)
Corboy Law Center (CLC) Room 0211 Campus map
25 E. Pearson, Chicago IL 60611
In 2002, the US Department of Justice and EU regulators ordered Microsoft to publish documentation sufficient to allow third parties to interoperate with hundreds of its server and client programs. This presentation highlights the novel requirements engineering and model-based testing devised to validate the resulting 60,000 pages of API documentation.
This process resulted in over 50,000 defect corrections. Lessons learned from this project can improve quality, reduce costs, and facilitate interoperability of any complex system.