My previous job was for a govt contractor. Test cases were a deliverable to the customer and there was never really a rush due to long development time. Average releases were 6 months. Since they were delivered to the customer, I would write them very detailed covering every user action from loggin in to loggin off, they were written so that anyone within the organization could follow. They were very functional but were mostly used to impress the customer with extensive documentation. (they were real pretty cases). Like I said, we tested at leisurely pace most of the time due to the slow moving expectations of the govt.
My new gig… I came as the only QA analyst and am responsible for new release testing, regression testing, etc. We are on a very agile release schedule here. We release every 2 weeks – new features components and fixed issues. We are working towards a monthly release in the near future. With the rapid development that we do here, I find myself simply out of time to write my detailed test cases like I used to. Most time is spent manual testing (these guys can produce some code at an unbelievable pace). I have also begun automating a lot of the regression testing but as I mentioned, due to time constraints it has been slow moving. Luckily I have another analyst joining us next week to ease up the load.
Anyways, I have discovered there is a quite a learning curve going from pokey govt development/testing to a pretty much extremely agile environment.
I am hoping someone here has a similar story and can offer some advice. My first step is to change the way I develop test cases. Im thinking since they are only used and presented internally I can get away with less detail and less formality. Is there a general usable template for this type of case? The main use here will be for documentation and CYA purposes.
I have the same situation inside one company (without moving to another). I actually hope to find time to update my blog at testingreflections.com with the story soon.
In short words I don't write ANY tests cases any more during testing cycle. I only update Test Plan that at the end of release has a very detailed "features tested" list with some hints and notes about features not working and bug IDs. Just after the release I do create test cases document details on how to invoke each feature, what input is expected by the feature etc. It is little bit like documentation, but have different goal/approach.
I try to use Testing Dashboard as replacement for formal test report with test cases executed/passed/failed/no executed. Sometimes I just communicate progress informally as my “gut-feeling”, and this is actually what PM wants to know, not the numbers of test cases.
?:the art of a constructive conflict perceived as a destructive diagnose.