Skip to main content

Let's Enhance the Student and Instructor Experience

Honing Instructor Materials is First Step


First in a series.

The Association for Software Testing (AST) is holding elections for its Board of Directors starting August 2nd at 12:00 a.m. (GMT) and running through August 4th at 12:00 a.m. (GMT). I’ve been nominated to run for the Board, and ask that you cast your vote for me.

My involvement with the AST is primarily educational. I’ve been a student in the AST's Black Box Software Testing (BBST) Foundations, Bug Advocacy and Instructors courses. I volunteer as an assistant instructor in the BBST Foundations class, working toward becoming an AST Certified BBST Instructor. I’m also a member of the AST’s Education Committee. So, when I was approached about running for the AST’s Board of Directors, it seemed to make sense that my focus would be on tester education.

I think education is integral to the AST’s mission of “advancing the understanding of the science and practice of software testing according to Context-Driven principles.” Tester education codifies and drives our objectives of hosting an annual conference to share testing practices, theories, and techniques, encouraging collaboration between testing professionals of all levels, publishing content on leading-edge theories and practices related to testing, and supporting the teaching of software testing. Education also serves as a foundation for several of the AST’s guiding principles, such as supporting the development of professionalism in software testing and fostering leadership in software testing through emphasis on personal growth in both ethical behavior and technical competence.

But “tester education” is a large and wide-ranging area of interest, and when I say that I want to focus on tester education it doesn’t really tell anyone much of anything about what I would work on if elected to the Board of Directors. So then, what exactly do I mean?

I want to work on improving three specific areas of tester education:
  • Update the BBST instructor materials so that the courses better meet the expectations of both the instructors and their students.
  • Work with the Board of Directors, the Education Committee, and the AST membership to find ways that make the BBST courses accessible to more people.
  • Research and establish alternate approaches to learning that better suit different learning styles.

I’ll discuss the first area of focus in this post, and the remaining two in follow-up posts.

Updating BBST Instructor Materials


The AST’s BBST courses are an integral part of supporting the development of professionalism in software testing. If you follow the AST News, then you probably saw the recent post What’s New In BBST, by Justin Rohrman, which talks about some of the recent changes that have been made in the BBST classes. The changes made so far have been high impact, and go a long way toward improving the student’s experience in those courses, but I think there are other areas of the courses that could be updated to further enhance the BBST experience for both students and instructors.

One such area is what we refer to as the Fieldstones. The Fieldstones contain pieces of well-written content which address topics likely to come up each time a course is taught. The idea is that an instructor can select an applicable piece from the Fieldstones, do some minor rework to better address the context of the current class, and use it rather than sending off a quick response each time. Use of the Fieldstones helps ensure that communication from the instructors uses a more consistent voice within the same class, regardless of which instructor is sending the communication, as well as across courses.

While the Fieldstones are beneficial, I feel that some of the pieces are starting to show their age. Others are incomplete, missing entirely, or show a single approach to a multifaceted problem and would benefit from additional input. This is a result, in large part, of the fast-paced nature of the course. Anyone who has been a student in a BBST course knows that it starts off at a fast pace, and only gets faster as the course progresses. The instructors face the same time crunch as the students do, so even though they may notice something in the Fieldstones that could be improved, they often don’t have time to make that improvement while the course is ongoing, or the improvement gets placed on the backlog where it may not be a high priority item until the next class.

Either way, I think we could help the AST better fulfill its objectives if we were to capitalize on the momentum generated by the recent updates made to the BBST courses, and organize a dedicated effort by members of the Education Committee and AST instructors to assess the current state of the Fieldstones, determine the target state we wish to reach, and then create and implement a plan for making updates to the Fieldstones across all of the AST’s BBST courses. By doing this, I believe that we can transform the Fieldstones from a good resource for course instructors into a truly vital resource that can be leveraged when teaching the class. This will, in turn, allow the AST to provide students with a better, more comprehensive and consistent learning experience.

Comments

Post a Comment

Popular posts from this blog

Takeaways from the Continuous Automated Testing Tutorial at CAST2014

I had the opportunity to attend Noah Sussman's tutorial on Continuous Automated Testing last week as part of CAST2014. It was a great tutorial, with most of the morning spent on the theory and concepts behind continuous automated testing, and the afternoon spent with some hands-on exercises. I think that Noah really understands the problems associated with test automation in an agile environment, and the solutions that he presented in his tutorial show the true depth of his understanding of, and insight into, those problems. Here are some of the main highlights and takeaways that I got from his tutorial at CAST2014. Key Concepts Design Tools – QA and testing are design tools, and the purpose of software testing is to design systems that are deterministic Efficiency-to-Thoroughness-Trade-Offs – (ETTO) We do not always pick the best option, we pick the one that best meets the immediate needs Ironies of automation – Automation makes things more complex and, while tools can make...

Let’s Continue to Drive Software Testing Education Forward

It’s Time to Embrace the Student Who Learns Differently Last in a series. In my last two posts I’ve written about enhancing the student and instructor experience in the AST’s BBST courses by focusing on updating the Fieldstones and making BBST courses more accessible by identifying some of the more common obstacles to BBST participation, and then working collectively to find ways to lower or remove those obstacles. In this post, I want to discuss the third and final area I would like to concentrate on if elected to the Board of Directors: researching and establishing alternate approaches to teaching that better suit different learning styles. As members of the AST, we have access to some of the best information and training available in the field of software testing. The AST hosts the Conference of the Association for Software Testing (CAST) each year, providing full-day tutorials, keynotes, and track sessions. They also offer four separate BBST courses:  Foundations, ...

Book Review - The Shape of Actions: What Humans and Machines Can Do

If you’re a tester and you’ve been around social media, attended a conference, watched a webinar, read blog posts, or watched videos of other testers speaking on YouTube, you may have heard at least one mention of polimorphic and/or mimeomorphic actions. But what does it mean when someone says that an action is polimorphic or mimeomorphic? Where do these ideas come from, and why, as testers, do we care? The concepts of polimorphic and mimeomorphic actions come from the book The Shape of Actions: What Humans and Machines Can Do, by Harry Collins and Martin Kusch. In the book the authors develop a new theory about what they call the shape of actions. I’ve attempted to cover the highlights and general topics of discussion, or at least what I found most interesting, from each chapter in the summary below. Chapter 1 – Humans and Machines In Chapter 1, Collins and Kusch introduce the reader to their theory which basically states that humans can do three things – they can do polimorp...