development lifecycles

In a world where technology is rapidly changing, development practices are quickly evolving, and teams are frequently reorganized, how can you remain steady and true to yourself? Even though things are changing around you, you can build a solid framework of personal beliefs to guide you throughout your professional career. To develop a credo-from the Latin “I believe”-is to take a personal journey through your professional life and the ideas that shaped it, ultimately creating your own statement of core beliefs. This credo forms a stable foundation for personal plans and actions. Marlena Compton shares the framework she’s used to build her professional credo. She examines manifestos and mission statements that have influenced her beliefs about building software and how she uses her credo as a basis to form concrete goals and take action.

Because the mobile market is extremely dynamic, maintaining consistent application quality is always difficult. Managing the risk exposures with mobile apps and embedded software requires comprehensive testing of a wide variety of platforms operating on multiple networks. Testers have to contend with short development cycles that require continuous QA efforts. Three key building blocks are required to overcome these obstacles: device-agnostic automation, access to a large selection of handsets and tablets, and ways to seamlessly apply your existing testing tools, skills, and knowledge to mobile. From his experience working with enterprises going mobile, Eran Yaniv shares the do's and don'ts for selecting an enterprise-grade mobile testing and automation platform, and offers his analysis of the advantages and disadvantages of the various approaches.

Remove software and service dependencies enabling continuous integration and testing across the development lifecycle. Stand up test environments faster and at a lower cost accelerating development and test cycles. Balance quality and speed - deliver high quality software faster.

Historically, performance testing has been relegated to simply adding a few weeks to the back end of a project to run a series of prescripted tests. The problem with this approach is that issues that performance test engineers uncover late in the project are often too costly to remediate, placing the entire effort at risk. Agile development methodologies can further complicate the issue due to their ever-changing landscape and often a lack of focus on performance testing. Eric Gee shares innovative ideas and techniques on how testers can engage as meaningful partners earlier in the software development lifecycle. Eric explores the benefits of partnering with software engineers in unit testing under load, testing at the component level, and other novel approaches you can use for early performance testing. If you are concerned about finding performance problems late in development, this session is for you.