Reddit reviews Agile Testing: A Practical Guide for Testers and Agile Teams (Addison-Wesley Signature)
We found 9 Reddit comments about Agile Testing: A Practical Guide for Testers and Agile Teams (Addison-Wesley Signature). Here are the top ones, ranked by their Reddit score.
Hey, fellow QA!
I got started as a QA Engineer about 6 years ago, and if you work in a studio where they use agile for managing their projects, I'd Recommend Agile Testing as a good book to get in the right mindset for handling QA tasks. The book is half an intro to Agile, and half how you can make the most of your QA position for the team.
Apart from that, I'd suggest reading up on automated testing frameworks. Microsoft CodedUI, Selenium, and scripting for programs like SOAPUI/Jmeter are great places to start. If you're considering staying in QA for the long term like me, having Automation experience gives you "expert" skillsets that really help your resume/salary potential.
If you've got any other questions about QA, feel free to ask! I've done a fair amount of freelance testing for games, and I'm currently working in enterprise software. Job market is much better for that where I live.
How Google Tests Software -- https://www.amazon.com/Google-Tests-Software-James-Whittaker/dp/0321803027
Agile Testing: A Practical Guide for Testers and Agile Teams -- https://www.amazon.com/Agile-Testing-Practical-Guide-Testers/dp/0321534468/ref=sr_1_1?s=books&ie=UTF8&qid=1493586342&sr=1-1&keywords=agile+testing
A Practitioner's Guide to Software Test Design -- https://www.amazon.com/gp/product/158053791X/ref=oh_aui_detailpage_o07_s00?ie=UTF8&psc=1
Agile Testing: A Practical Guide
Continuous Delivery
Clean Code
Obviously, after this you can expand more in the direction of your particular product needs. I've been doing a lot of reading around CI/CD process, and the overall trend towards "DevOps". But you might want to focus on security or performance testing, and that will have its own path.
Too many questions :)
I think you should start with unit tests, at some point you will reach the high level interfaces by which your application communicates with the external world (or simply with other components). There, you'll slowly start realising your tests target the behavior of your application rather than assert that your code computes B from a given input A.
It's not always clear what should be called functional or integration testing but with some experience you may get a better feeling for it.
A book that might be quite helpful to start your quest.
In addition you may read this. Though they focus on agile development teams, they still can be relevant.
Perhaps you can try working part-time in remote crowdsourcing test platforms. You'll get exposed to different types of products and learn quickly how to approach testing strategically.
https://www.amazon.com/Agile-Testing-Practical-Guide-Testers/dp/0321534468 -- I read this while I was still a working student in QA, to understand how QA works in dev teams.
Read up more about: BDD, Gherkin, blackbox testing
Cool :)
I would start with CD book https://www.amazon.com/Continuous-Delivery-Deployment-Automation-Addison-Wesley/dp/0321601912
Having read it you would understand how modern software development look like and you should understand why test automation is crucial these days.
I had once created a post about learning test automation - you can check it here
http://www.awesome-testing.com/2016/08/how-to-start-learning-test-automation.html
Here are two paths I proposed:
Path 1 - GUI Automation with Selenium
Path 2 - REST API Automation with Rest-Assured
There are a couple of testing books which are worth reading too. Perhaps this one is the best https://www.amazon.com/Agile-Testing-Practical-Guide-Testers/dp/0321534468
Just start small with basic checks. You may even use my github project https://github.com/slawekradzyminski/AwesomeTesting
Hope I hadn't overwhelmed you :D
I concur with learning a programming language, however I disagree with learning python, not that isn't a bad idea to learn it, but for automation I would suggest ruby actually....as a lot of the automated testing uses ruby (or ruby on the backend)...it's a pretty easy language to learn.
Automation is HOT right now, literally I get people adding me on linkedin JUST because I put "automation" or "selenium" on there. It's crazy at how in demand it is.
It's actually really not that bad to learn either, my programming is Rusty (I also graduated with a CS degree like 7 years ago) so you probably still have the "ability" to pick it back up easily.
I'd also suggest this book on agile testing : https://www.amazon.com/Agile-Testing-Practical-Guide-Testers/dp/0321534468
It's a pretty well-known and referenced book.
As for Automation i'd suggest trying it out on an External Site and using Capybara with Selenium AND Poltergeist drivers. Capybara is a DSL and helps sort of...shorten the commands needed per driver (Such as click_button in all Drivers as opposed to using Seleniums driver specific button clicking method).
Poltergeist is a headless driver that uses Phantomjs, so it's perfect for Continuous Integration (Recruiters love that word). So it's worth learning to say you know how to write automated tests for a CI environment.
If you have any questions on automation let me know, I do it everyday as a QA where I work.
Agile Testing by Lisa Crispin is one of my favorite testing books.
Agile Testing is solid on principles. Don't be scared of the agile label, it's a sound foundation for understanding test automation.
I'm not sure what you mean by "from a DevOps perspective" though. To use an extreme example, if the test engineers are writing Selenium tests and running them locally in a QA silo, reading a book about modern test automation isn't going to help you communicate with them.
You'll be showing up in a tuxedo to find everyone else is wearing jeans and an old Mickey Mouse t-shirt. Yes, you're both wearing pants and your torso is covered, but that's about where the common ground ends.