Category Archives: Documentation

When Low Priority Bugs Should be Fixed

TweetSo you file a UI issue. No functionality is broken, the site looks ok. The deadline is close, and it makes sense to launch it. No one wants to delay a deploy because of a few pixels. When do you … Continue reading

Print Friendly
Posted in Documentation, Mindset, Processes, Teamwork | Tagged , | 6 Comments

What I've learned about Agile Testing

TweetI started on an agile team last August. In the past few months, I’ve be exposed to a wide range of agile-ness as we have learned to adapt it for different projects and struggled to make it work for us. … Continue reading

Print Friendly
Posted in Agile Development, Documentation, Goals, Manual Testing, Processes, QA jobs, Requirements Document, Test Plan | Tagged , , , | 2 Comments

Write bugs that get fixed

TweetIt seems simple enough- find an issue, file a bug, wait for it to be fixed. The tough part should be finding the bug in the first place, but sometimes it isn’t. 1- Time constraints. When deadlines loom, the team … Continue reading

Print Friendly
Posted in Documentation, Processes, Teamwork | Tagged , , , | 2 Comments

Documentation on Agile Developement Teams

TweetAgile Teams are all about flexibility, right? Rules evolve with the project, people’s suggestions can taken on, deadlines can be adjusted internally – and within that one week sprint, the team is pretty much free to set their own pace … Continue reading

Print Friendly
Posted in Agile Development, Automated Testing, Documentation, IEEE, Processes | Tagged , | Leave a comment