Book a Demo

Author Topic: Test Cases  (Read 2542 times)

cheesman

  • EA Novice
  • *
  • Posts: 10
  • Karma: +0/-0
  • I could murder a pint
    • View Profile
Test Cases
« on: January 26, 2007, 09:45:09 am »
I'm a bit confused again ???

What is the purpose of having the Test Case item in the (Maintenance) toolbox and the Test Cases in the 'Testing' window?

The latter seems to contain the right info for recording a test case such as Acceptance Criteria, who ran it etc. whereas the Test Case in the Toolbox seems to be entirely different.

Wouldn't it be good to be able to define Test Cases, as defined in the Testing window, by dragging the Test Case item from a Toolbox?

Regards

Cliff

bioform

  • EA User
  • **
  • Posts: 230
  • Karma: +0/-0
  • Forty-Two?
    • View Profile
Re: Test Cases
« Reply #1 on: January 30, 2007, 08:46:40 am »
Just another feature that you can decide HOW you want to use it!

For instance I use the "Testcase" object to map my End-to-End system tests that cross use cases.

For example:
Create Testcase named "Manage Loans", then I could create scenarios that could be "Process New Load Applications", "Send End of Loan Thank-Yous", "Send Need Another Loan Ticklers", etc.

Each of these scenarios would represent a business process, that is composed of several different types of interactions with the System Under Design (the UC's named scenarios). So then within the testcase, I would create a test for each testcase scenario I defined, and then build them up using references to the system use case scenarios that would be appropriate (e.g, UC A, Scenario 1 then UC D, Scenario 5, then UC B, Scenario 3, etc.) until the process has been defined... and now can be managed as a end-to-end test of the system...

EA has a very flexiable approach to testing, you just need to come up with a style/approach that works for you...
Time is what keeps everything from happening at once, Space is what keeps it all from happening to you. <unknown>