Accelerating the writers in the community.
A community-driven co-writing space that aims to support and inspire talented writers in tech industry(mainly QAs) by bridging the gaps between knowns and unknowns!.
We are a non-profit community driven co-writing platform that aims to connect and find the rich voices, ideas & experiences among the community that are usually lost somewhere. We aim to provide that platform for FREE where people from the community will be providing feedback and working together to improve your writing skills.
Get in touch:
contact@synapse-qa.com
Follow us:
20+
Writers
40K+
Views last year
60+
Articles last year
Want to be part of us?
We’ve had an incredible response so far, and are doing everything we can to respond to everyone who wants to be part of Synapse QA family.
Hear more from us.
Super Reads Lounge is LIVE! Check it out.
Bug Advocacy-An Effective Way of Writing A BUG
The excellent bug report raises the issue and provides sufficient data for a good decision.The article describes why do programmers do not fix some bugs so how to report bugs accurately so that the reader understands the impact of the problem and takes up for fix.It describes RIMGEN a guide for how to investigate bugs and communicate better.It also describes about some good Bug reporting skills for a Tester to improve his credibility.
Where are the testers on the spectrum?
My thoughts on the concept of shift left in software testing.
1. Shift left simplistically applied to automating everything in sight is not an ideal solution.
2. Morphing all the diverse roles in software engineering to just have all programmers on team leads losing knowledge present with people who understand different facets of creating software.
3. Leaving testing to the end of a project is not a solution either.
“So many things are possible just as long as you don’t know they’re impossible.”
Norton Juster
