In an ideal world we'd have Acceptance Tests-->Unit Tests-->Integration Tests-->Test Plans and Automated GUI Tests (With Selenium or something).
But where does it start to get cut out when you just don't have the testing resources?
Unit Tests are usually created by devs, so thats less of a problem.
But Test Plans/Integration Tests (With Rspec/Cucumber/etc...) and then writing Plain ol Test Plans (Old school style: Expected Result/Actual Result/Steps/etc...)
Im the Sole QA, so with multiple projects it's basically impossible for me to do so, the company is rather small...so hiring more testers/QA isn't always the option. 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?
To me, they seem lengthy and time consuming, and also take away any possible "Automation" R&D and implementation, which is what I'm really struggling with. However Automation and implementing some sort of CI process also takes a lot of time, which could be used for writing test plans.
Right now i've been researching Automation testing in my spare time trying to figure out the best course of action, while doing exploratory sessions and recording the bugs in Excel (Lame I know, but I gotta start somewhere)....Where do you go from here?