Tag Info

Hot answers tagged

6

The short version: regardless of the development methodology, your role is to provide information about the overall quality of the application. You do that via testing anything that isn't included in the developer-maintained automation, and reviewing the developer-maintained automation. The long version: This question and its answers is a good starting ...


3

According to me, you should not go for a ready made checklist. More appropriate way is to develop your own checklist. Understand you requirements, analyse them and then sort it in a form of a checklist. Then you can get feedback or opinions of others and see if it is adequate or if it need any improvement...


2

Actually, we're doing this exact thing you mention. Testing in the same three weeks as development is nefarious for testing time and quality overall, as you seem to have experienced. So, we're testing for two or three weeks after the development sprint has finished. By delaying testing for a few weeks, you'll be working on a fully delivered sprint ...


1

Only you can really answer that. A good testing framework that can run functional test automation is software, like any other; you'd have to write it and maintain it, but you might find it easier to add tests when you don't have to worry about flakey record-and-playback, and once you have a decent framework, other developers can pitch in and write tests ...


1

Your requirements seems to describe document-heavy proprietary process. Unlikely examples of such process would be posted in the open: usually you pay consultants nice hourly rate to teach you/explain you how their process works. Only salesmen (before you fork the money) are free. Call me a pessimist but I know that snake oil is much easier to sell if ...


1

The second and third bullet points are arguably not bugs at all. They're new feature requests. Invent a list where anyone -- testers, programmers, marketing, subject matter experts -- can suggest a new feature. Sticky notes on a wall will do. That new request gets prioritized like any other request. (By contrast, a policy might be that regression bugs must ...


1

We can't tell you how to fix your process because it depends on your own circumstances. That said, this does not sound like a hard problem solve. It sounds as if your Jira configuration is not expressive enough for your workflow. If it were me, I would do start by getting agreement on which workflow problems need fixing. It sounds as if you already have ...


1

Maybe you will find a predefined checklist somewhere. But How will you be sure that it is appropriate or correct? What if its not really for you? Will you just take the word of somebody without understanding your needs?


1

Hanu Kommalapati and William Zack layout a generic plan for the SaaS SDLC at http://www.infoq.com/articles/SaaS-Lifecycle.



Only top voted, non community-wiki answers of a minimum length are eligible