We can agree that testing is important for software development, but how and what we test is not so straight forward or agreed upon. Extending beyond unit, integration, and acceptance or end-to-end testing, our solutions need to also consider security, performance, load, usability, and exploratory testing. When there’s always another bug lurking on the periphery, it’s perhaps most important that a team considers the levels of testing their solution demands and agrees upon a testing plan that outlines responsibilities and expectations. From non-functional requirements to data management, from third party integration to environments, we’ll discuss levels of consideration for maximum extermination.

Speaker: Michael Leners

Michael Leners is a software developer who transitioned from a career in science and education. He is passionate about front-end best practices and user experience – both for the end-user and developers as users. He is currently exploring this field as part of the Fuse within Cardinal Health in West Des Moines, IA. Michael enjoys fun and games, but he gets the biggest thrill from collaborative learning and teaching. He is an advocate for minorities in STEM, loves to dance, and geeks out on data.

Social Media:

https://github.com/micleners

https://www.linkedin.com/in/micleners

Sponsor: Dynamo

Getting it right — the first time — shouldn't be so radical. By turning more, more, more into better, better, better, we’re redefining the IT solution. By placing people over transactions, we’re changing the way value is created in consulting and recruiting.