Tag Info

New answers tagged

0

We have recently launched http://backtrac.io project that also allows you to run set of screenshots and compare them. One of main features right now is ability to compare your production and staging environments. In this way you can see what is going to be changed very efficiently and in this way catch bugs early.


1

I'd like to add two more points which will be difficult for firms but as this topic is not limited to this (at least in my opinion) two other possibilities. Both can't be done by QA only. 1) Make your code open source. By making the code open source you'll get more reviewers and more feedback on source code and there will be more installations of your ...


1

You mentioned having a handle on testing, but wanting to know more about documentation in limited time scopes. In that case, my advice would be to get into Jira or another bug-tracking software asap. I like to keep a regression testing google doc spreadsheet which I then insert links to relevant bugs in Jira. That way you, fellow testers/devs/PMs, can all ...


1

Kate is dead-on with her suggestion about the short version. If you are REALLY pressed for time, these are the steps I take: You want to save your team time and pain, and you do that by focusing on potential issues that are going to be much less costly if we catch them sooner rather than later. I usually start by asking myself "what feature(s), if broken ...


1

The first three things that come to my mind are: Can you get the product owner to test new functionality? As they know what they want (as opposed to what they asked for) Don't have a test plan, have a one page check list that you can print off and tick off, just so you don't forget any major areas of functionality. Start automating simple things, and ...


1

It seems to me that having Acceptance Tests is a must have, and possibly testing sessions for bugs...but I'm wondering if the old school type of test plan....really make sense? Acceptance tests are based on a ticket's Acceptance Criteria. A testing session for bugs... I think you mean a smoke test. Which I advice before every deployment, at a minimum. ...


5

The short version: Don't sweat on automation or test cases. Chances are you won't get time to build it because there's too much that has to be manually tested now. Instead focus on building light-weight, easy to maintain documentation of the key elements of the software you're testing. The longer version: This is my world. I'm the sole tester in a team of ...


2

Ouch. No, the old school sort of test plan doesn't make much sense in your context. The only reason I can see for doing them is if you had a contractual requirement with a client to deliver them. Will anyone read them except you? (If no - then stop doing them now!) If you re-read them, what do you use them for? To remind you of how to do something (is it ...


1

Both Acceptance tests and Integration tests could be either manual or automated. Unit tests make sense ONLY automated, and I assume your developers write unit tests (as they should). Start with manual testing most often used and most recently changed functionality first, where detecting a problems has best value for time invested. But ask your manager for ...



Top 50 recent answers are included