SOBRE ESTE EPISÓDIO
In this episode we’ll be talking about the QA role on an agile team, skills and knowledge beneficial to this role, and how developers and QA can work together collaboratively.
Today we’re happy to welcome Peggy Sturman to the show. Peggy has been a long time listener and supporter of the show. We met her through our Slack channel where we often have discussions around technologies we’re learning, career and interview advice, and thoughts about the field in general. She has nearly two decades of Quality Assurance experience and is currently learning about software development and coding in her free time.
Welcome to the show Peggy! Is there anything else you’d like our listeners to know about you?
“‘Sharpening the Tools’ is the section of the show where we discuss what tools we’re using, concepts we’re learning, and generally how we are continuing our learning in software development.”
===============
* If you were to describe Quality Assurance in an elevator pitch, how would you describe it?
* Quality Assessment, trying to break the application
* Did you have any formal education to prepare you for working in QA? If so, did you feel adequately prepared for your first QA role?
* Can you take us through a typical day as a QA Engineer?
* What technologies and tools do you use?
* What’s the structure at your job? Are you doing QA for multiple teams / projects?
* What allows your team members/software developers to help you do you your job effectively?
* You’ve talked about learning to code in your free time, what languages and frameworks are you learning? How are they coming along?
* Do you feel that your QA experience helps when learning code, and / or does learning code help with your QA role?
* Black box testing – also known as Behavioral Testing, is a software testing method in which the internal structure/design/implementation of the item being tested is not known to the tester. These tests can be functional or non-functional, though usually functional. http://softwaretestingfundamentals.com/black-box-testing/
* Smoke testing – also known as “Build Verification Testing”, is a type of software testing that comprises of a non-exhaustive set of tests that aim at ensuring that the most important functions work. The result of this testing is used to decide if a build is stable enough to proceed with further testing. http://softwaretestingfundamentals.com/smoke-testing/
* Regression testing – s the process of testing changes to computer programs to make sure that the older programming still works with the new changes. Regression testing is a normal part of the program development process and, in larger companies, is done by code testing specialists. https://searchsoftwarequality.techtarget.com/definition/regression-testing
* What would you tell someone interested in learning about or exploring Quality Assurance? Are there certifications you can get? Recommended resources?
* https://www.ministryoftesting.com/
* What’s something you wish you knew before starting this role?
Peggy’s LinkedIn: https://www.linkedin.com/in/psturman/
References
==========
https://www.ministryoftesting.com/
Extra Links
===========
You can reach us at helloworld@juniordevelopertoolbox.
Today we’re happy to welcome Peggy Sturman to the show. Peggy has been a long time listener and supporter of the show. We met her through our Slack channel where we often have discussions around technologies we’re learning, career and interview advice, and thoughts about the field in general. She has nearly two decades of Quality Assurance experience and is currently learning about software development and coding in her free time.
Welcome to the show Peggy! Is there anything else you’d like our listeners to know about you?
“‘Sharpening the Tools’ is the section of the show where we discuss what tools we’re using, concepts we’re learning, and generally how we are continuing our learning in software development.”
===============
* If you were to describe Quality Assurance in an elevator pitch, how would you describe it?
* Quality Assessment, trying to break the application
* Did you have any formal education to prepare you for working in QA? If so, did you feel adequately prepared for your first QA role?
* Can you take us through a typical day as a QA Engineer?
* What technologies and tools do you use?
* What’s the structure at your job? Are you doing QA for multiple teams / projects?
* What allows your team members/software developers to help you do you your job effectively?
* You’ve talked about learning to code in your free time, what languages and frameworks are you learning? How are they coming along?
* Do you feel that your QA experience helps when learning code, and / or does learning code help with your QA role?
* Black box testing – also known as Behavioral Testing, is a software testing method in which the internal structure/design/implementation of the item being tested is not known to the tester. These tests can be functional or non-functional, though usually functional. http://softwaretestingfundamentals.com/black-box-testing/
* Smoke testing – also known as “Build Verification Testing”, is a type of software testing that comprises of a non-exhaustive set of tests that aim at ensuring that the most important functions work. The result of this testing is used to decide if a build is stable enough to proceed with further testing. http://softwaretestingfundamentals.com/smoke-testing/
* Regression testing – s the process of testing changes to computer programs to make sure that the older programming still works with the new changes. Regression testing is a normal part of the program development process and, in larger companies, is done by code testing specialists. https://searchsoftwarequality.techtarget.com/definition/regression-testing
* What would you tell someone interested in learning about or exploring Quality Assurance? Are there certifications you can get? Recommended resources?
* https://www.ministryoftesting.com/
* What’s something you wish you knew before starting this role?
Peggy’s LinkedIn: https://www.linkedin.com/in/psturman/
References
==========
https://www.ministryoftesting.com/
Extra Links
===========
You can reach us at helloworld@juniordevelopertoolbox.
Inglês
Estados Unidos da América
TRANSCRIÇÃO 🔗
Are you the producer of this podcast?
Add a podcast transcript
Need Audio-to-Text?
Transcribe with Listen411 in Just 60 Seconds
PESQUISAR EPISÓDIOS PASSADOS
Pesquisar episódios anteriores de Junior Developer Toolbox.
OUTROS EPISÓDIOS NESTE PODCAST
In this episode we’ll be talking with Dan Weese about his perspective on interviewing and assessing developer candidates, and building strong teams.
‘Sharpening the Tools’ is the section of the show where we discuss what tools we’re using, concepts we’re learning, and generally how we are continui…
In this episode we’re diving deeper into Agile and Scrum, and continuing our exploration of various tech roles. We’ll have a chat with Becca Hiller about what she does as a Scrum Master.
We’re excited to introduce a special guest on this episode: Becca Hiller has worked as a Scrum Mast…
Today we’ll be talking about Scrum! We explore roles, ceremonies, and more! We’ll discuss the agile manifesto and our experience working with this project management style.
“Sharpening the Tools”
Erin:
I honestly haven’t had a whole lot of time the past few weeks between moving and tak…
In this episode we’ll be discussing Alon’s role as a Security Service Delivery Lead, how he applies digital anthropology to his job, and security issues facing companies and developers.
Alon’s IT career spans academic, start-up, and corporate environments. His experience ranges from software devel…
In this episode we’ll be talking about giving your brain a break! We’ll touch on strategies for recovering from mentally taxing work, and the importance of taking time for ourselves.
“‘Sharpening the Tools’ is the section of the show where we discuss what tools we’re using, concepts we’re learning…
Aviso: O podcast e a arte incorporada nesta página são de Erin Orstrom & Dave Harned, que é propriedade de seu proprietário e não é afiliado ou endossado por Listen Notes, Inc.
EDITAR
Obrigado por ajudar a manter a base de dados dos podcasts atualizada.
