We were lucky enough to get another inspirational women to do an interview for uTest.
Alison Wade is an accomplished executive dedicated to the business of software. For the past fifteen years, she has worked with industry leaders developing programs for software development and testing professionals. Alison has been instrumental in building Techwell, a company with an outstanding reputation for delivering high-quality services, publications, events, and partnerships. With experience working in more than a dozen countries, her expertise includes: leading teams, business development, strategic partnerships, and agile software development. Alison is a Certified ScrumMaster and Product Owner.
Alison is also the program chair of Mobile Dev + Test Conference. She plays a pivotal role in the development of the Better Software, Agile Development Practices, DevOps Conferences, and STAR Conferences in the USA, in addition to directing Software Quality Engineering’s highly respected training curriculum and programs. She strives to increase awareness of diversity in the software industry with regard to both the workforce and the role of software beyond commercial products and IT departments.
In 2015, Alison launched Women Who Test, a day dedicated to women software engineers, which will happen in conjunction with the STARWEST conference.
Read more: StarWest Women Who Test
Through her work as a board member of Humanitarian ToolBox, Alison brings her years of experience to leverage technology and help skilled volunteer communities solve the needs of response organizations and communities affected by natural disasters.
Follow her on Twitter @awadesqe
With Alison’s admirable career and dedicated strides she has made a huge impact to encourage women testers. We are so excited to share what she had to say because her ideas can help you be a better tester and help us become a better resource for women.
How did you begin your career in testing?
A: I had no clue I was testing when I broke my first Macintosh in 1985. While I was still in school, I was lucky enough to work part-time at a very progressive company, and they purchased one of the earliest Macintosh computers. The sales rep, yes he came to our office, delivered to it me with a headset and a cassette deck. I took a tutorial via cassette tape to learn how to use it. Within hours, I managed to render it unusable and the sales rep had to pick it up. He later came back and told me “you did things to the software on that machine you shouldn’t have been able to do, how did you do that?” Tester born!
In the early 90’s I worked with a couple of developers to create some proprietary software that scheduled over 10,000 individual face to face appointments for thousands of users, over a two day period. It was impossible to test everything, and so I created a complex set of tests to validate that the software was functioning correctly. I had no idea I was writing a test plan and practicing risk-based testing. However, I did know if the paying customers didn’t get the appointments they requested, my life would be hell, so I needed to make sure the system worked.