New QA person, C# Testing looking for guidance
I have been hired as a Quality Assurance developer at a library software development company. I have been working here for about 6 months. My current role involves me doing integration testing for an api among other things. I have previously had some experience with Java and C# but this is my first job as a Quality Assurance person. All my testing is currently done in C# using MSTest Framework.
My question is, Quality Assurance (development or engineering not really sure of the term) seems to be a very broad and abstract role. Is there any books or sites or anything that i could read that could enhance my career? I am trying to learn as much as i can about developing testing software in C#. I am welcome to theory, best-practices, implementation, anything that you guys think would help in terms of enhancing my knowledge base. I would also like to mention that i am the only QA developer at my organization. There is a QA team with no coding knowledge and a development team with no QA knowledge and i am in the middle
Thank you for your help
In terms of couple books that'll help you get settled into QA career,
I'd recommend Jame's Whitaker's book, how Google Tests software.
The chapters are divided into different roles within Google's QA and SDET positions, what they do, and how to interview/hire someone who would be a good fit in those roles. I think that book will give you a better understanding of your scope of responsibilities.
Another book i'd think would be good to read later as you get more settled in is a Practitioner's Guide to Software Testing, by Lee Copeland. That book covers little of alot of things. It's a good way to learn about test/coverage theory, risk mitigation, and how to handle common real world situations dealing with QA.
head first C# want to try?
I think the book, Lessons Learned in Software Testing , I'd probably put as maybe the 5th or 6th book to read. That books is a bunch of anecdotal stories by various testers that speak at the SQA conferences. Most people think of it as a more quotable book than being useful. But there are various good nuggets of info in this book, and I think having things to quote from really helps you make your point to the higher ups when there's a lot of pressure to ask you to speed things up or skip a step to make release dates.
Originally Posted by Joe Strazzere