I was wondering if I could get a few pointers from some more seasoned QA/Testers.
I have a budget tool and reports to manually test for functionality. The system is web based and build on Oracle. There are quite a bunch of different test cases for both the tool and reports.
How would you organize your testing? Would you split the test cases by test case type(func,GUI) or would you keep it sequantial by the flow of the program? Does one outweight the other in terms of being cost and time efficient?
Lynn gave you a good answer. Let me add my 2c: I'd first break down all requirements for tracebility. Then, I will create various workflows (from the users' perspective) to test those requirements. So that way, you can test how the application works the way it is intended and also its requirements are also verified. One caviat: you might have multiple workflows that verify 1 or more test requirements.