meta user
network profile
| bio | website | itester.co.uk |
|---|---|---|
| location | United Kingdom | |
| age | 29 | |
| visits | member for | 2 years, 1 month |
| seen | Jun 4 at 12:30 | |
| stats | profile views | 21 |
I'm currently working as a Lead Test Engineer and trying to turning the testing world on it's head.
|
Jul 1 |
comment |
What are the best tools available to test performance of a MVC web site What technology stack are you using? .net, java...? |
|
Jun 30 |
comment |
Testing webservice engine: best practice +1 if this is what you are doing then the person that wrote the parallel application should just write the main application, cause obviously he's done it correctly! Then you wouldn't need to test it :) |
|
Jun 21 |
comment |
What is the difference between sanity and smoke testing? They are not the same thing, unfortunately this is common mistake in software quality assurance. They do share similar characteristics, however, they serve a different purpose. |
|
Jun 14 |
comment |
Documenting Unit Tests great response, thanks for posting! |
|
Jun 14 |
comment |
Documenting Unit Tests They mostly deal with the internals details of the implementation |
|
Jun 14 |
comment |
I Can't Shut Down My Selenium Instance (C# WebDriver, Gallio). I think I have a bug… @Lyndon You still need to run the selenium server to get the Remote Web Driver to work. We tend to use this to allow our test to be run on a another machine rather than the build server. You also need it in .net to run the headless browser (HtmlUnit). |
|
Jun 10 |
comment |
Workflow shortcut to meet the release deadline "QA specialist should not be involved in the actual gathering / creation of the requirements." At the end of the first sentence in your answer. Apart from that you make some great points such as not letting letting the process become a bottleneck. |
|
Jun 10 |
comment |
Workflow shortcut to meet the release deadline I strongly disagree with a QA specialist should not be involved in the creation of requirements. From experience, I have found that getting testing involved from the start of a project (requirements creation) has helped us catch bugs or potential bugs before any time has been wasted on writing code for a component that would be fundamentally flawed. |
|
Jun 8 |
comment |
Test Strategy Documentation I feel that people skim rather than read if they are presented with a large document on a dry subject. |
|
Jun 8 |
comment |
What factors should affect the ratio of QA/Test staff vs. App Developers Good question, I was just about to ask the same! |
|
Jun 7 |
comment |
Developing Unit Tests While Refactoring Legacy Code? +1 - again for Working Effectively with Legacy Code book |
|
Jun 6 |
comment |
is it appropriate to do exception handling for every single test method? I agree, your test framework/runner should deal with catching exceptions. If you feel that you do need to catch an exception then you should catch the exact type, not a general exception in case you catch something that you shouldn't have. |
|
Jun 1 |
comment |
Are state transition diagrams a good software testing technique +1 Great answer! |
|
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 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 |
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 11 |
comment |
1.5 Million lines of code. 0 tests. Where should we start? +1 for this book, it's definitely worth it! |
