| bio | website | itester.co.uk |
|---|---|---|
| location | United Kingdom | |
| age | 29 | |
| visits | member for | 2 years |
| seen | Mar 20 at 18:49 | |
| stats | profile views | 21 |
I'm currently working as a Lead Test Engineer and trying to turning the testing world on it's head.
|
May 31 |
answered | XSS/CSRF security testing |
|
May 26 |
awarded | Critic |
|
May 26 |
accepted | What are the benefits of Block Testing? |
|
May 25 |
asked | What are the benefits of Block Testing? |
|
May 19 |
accepted | Behaviour Driven Development with JavaScript |
|
May 19 |
asked | Behaviour Driven Development with JavaScript |
|
May 18 |
comment |
How do you fit regression into Kanban? @testerab Yeah, you definitely don't have that testing squeeze at the end of a sprint when someone's estimates upstream of you is way out. |
|
May 18 |
comment |
How do you fit regression into Kanban? @testerab No worries, If you are wanting to do further testing then you can do this when the work item is in the testing state, however, if you are going to use these for regression testing then I suggest you automate them and execute as part of your continuous integration. Do not move the work item until you have done all your testing. |
|
May 18 |
comment |
How do you fit regression into Kanban? @testerab I didn't say that I allow one hour for exploratory testing, I said set a fixed time period to perform exploratory testing each week (you could do an hour each day if you want more), the duration depends on what you think is appropriate. Only do this in the allocated time as you priority is to move the work items through the workflow, so you should focus on moving the work items in the test state to the next state on your workflow. You can deploy at any time, this doesn't happen after exploratory testing, it usually happens when a work item enters the deployment state. |
|
May 18 |
answered | How do you fit regression into Kanban? |
|
May 17 |
answered | How to plan security testing of a web application? |
|
May 17 |
comment |
Fitting regression testing in a Agile/ Scrum development cycle This is some good advice, you should automate as much as possible. If you get to the end of a sprint and you have to manually testing new features you should add a post-it note to a board somewhere so that you can see when you are building up a manual regression suite, this will help indicate when you need a hardening sprint to reduce the manual testing debt you've acquired of the the previous sprints. Also, have the whole team do some exploratory testing before the end of the sprint, this will catch the fringe cases and usability issues. |
|
May 17 |
awarded | Scholar |
|
May 17 |
accepted | How do you calculate your return on investment on automated tests? |
|
May 17 |
comment |
How do you calculate your return on investment on automated tests? I've used this approach, we invested 5800 hours approx. which saved the project team form executed around 28000 hours approx, a total saving of 22200 hours (again approx.)! |
|
May 17 |
comment |
How do you calculate your return on investment on automated tests? Our regression suite is there not to find new bugs but to give us a clear indication that the build is good enough to perform further testing. I think that it is important to have a deterministic regression suite and have another suite for fuzz testing that will try to find new defects. |
|
May 17 |
answered | What measures do you use to assess software quality. |
|
May 11 |
answered | Testing Distributed Systems |
|
May 11 |
comment |
1.5 Million lines of code. 0 tests. Where should we start? +1 for this book, it's definitely worth it! |
|
May 10 |
comment |
How do you calculate your return on investment on automated tests? Priceless is the real answer, however, I it would be nice to know the actual cost. |