CAST 2016 has ended
Testing: Software Development Catalyst

Testing is not an isolated activity. It interacts with and influences other disciplines in software development such as design, coding, release management, and deployment. As testers, our skills and experiences add value far beyond the immediate context of verifying functionality. Threats to value other than software errors exist.

Yet our discussions are often constrained to the testing space, omitting the connections to, and dependencies on, other roles and activities. Testing is an integral discipline of software development, and often plays an active and important role in bridging gaps between technical and business-focused roles, between leaders and engineers, and between makers and users.

How does the testing piece fit into the software development puzzle? How does – and how should – testing interact with other disciplines in software development? How can we most effectively add value to the software development projects we participate in?

Please join us for our 11th annual conference at the Simon Fraser University Harbour Centre campus in downtown Vancouver, Canada, August 8-10 2016.


IMPORTANT NOTE: Creating a profile on this site does not constitute registering to attend the conference. If you would like to attend and have not yet registered, please Learn More »

Tuesday, August 9 • 11:00 - 12:00
Embedded Testers Aren’t Undercover Cops

Sign up or log in to save this to your schedule, view media, leave feedback and see who's attending!

Life as an embedded tester is awesome.
It’s the perfect position for a tester to influence the way software is produced instead of just waiting
for whatever the great development machine pumps out at the end of each cycle.
It’s also challenging, frustrating and sometimes confusing, but if you do it right; it will kick you out of
your comfort zone and make you question everything you learned so far about making better
Last year I was the first embedded tester at a company, surrounded by people who knew nothing
about what I do as a tester, but as the team grew, so did the acceptance of our role.
Developers, product owners and architects started to value and rely on the work we do and our
input was incorporated into the software delivery process.
Deciding how we wanted to do our jobs and standing by our decision opened the door for us to
become valuable players in the development game and established a context in which testers
stepped out of the scenery and into the story.
Thinking back on my previous roles – both as an embedded and an independent tester – I realized
that the principles are the same:
• Own the product. We have the same goal, so each of us has to take responsibility.
• Don’t believe the hype. Agile or not; the solution that suits the project best is the one to go with,
regardless of the latest trends.
• Watch the methods. Both in development and testing. No point criticizing the outcome of a
process we know isn’t right for the project.
• Roll with the punches. A project in a transitional phase cannot afford to get stuck with processes
that don’t work.
Much of what I’m going to talk about can be especially useful for testers working in independent
teams. Simply realizing that you’re not the only one concerned with quality can change your attitude
and that change can catch on quicker than you think.

avatar for Sandor Boros

Sandor Boros

Software Testing, Data, Bioinformatics

Tuesday August 9, 2016 11:00 - 12:00 PDT
Labatt Hall (1700) Simon Fraser University Vancouver 515 West Hastings Street Vancouver, BC V6B 5K3