geldfeld
asked on
Acceptance Testing Frameworks
I need clarification on how an Acceptance Test (AT) may be automated.
I use Unit Tests extensively already but I am a little confused on how may an acceptance may
fits into the picture.
I do know that the AT must be given a high-level description, but how does this map to code?
I use Unit Tests extensively already but I am a little confused on how may an acceptance may
fits into the picture.
I do know that the AT must be given a high-level description, but how does this map to code?
ASKER
@pepr - I have read the Acceptances Tests can be automated, yet they are defined in high level langague by the business users. What are the steps in between, mapping the high-level description to the test scenario.
This is not what I am clear about.
This is not what I am clear about.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
@pepr - this has covered the issues that I needed resolved regarding Acceptance Testing.
The article from Martin Fowler were especially helpful
The article from Martin Fowler were especially helpful
To make it simple, unit test is done by developer to ensure the functional point works.
To do a Acceptance test, you need to study the software requirement, think about what actual that user expectation.
You should not try to "map" it code (and.....actually you don't need to)
for example, let's say you are developing a image editing software, and you have developed lots of complicated image editing functions (and you did extensive unit test on it). The acceptance test may be just simple as:
Test Case 1: Open and close application
Test Case 2: Open a JPG image
Test Case 3: Open a BMP image
Test Case 4: Apply blur filter to opened image.
that's it.
To do a Acceptance test, you need to study the software requirement, think about what actual that user expectation.
You should not try to "map" it code (and.....actually you don't need to)
for example, let's say you are developing a image editing software, and you have developed lots of complicated image editing functions (and you did extensive unit test on it). The acceptance test may be just simple as:
Test Case 1: Open and close application
Test Case 2: Open a JPG image
Test Case 3: Open a BMP image
Test Case 4: Apply blur filter to opened image.
that's it.
This question has been classified as abandoned and is closed as part of the Cleanup Program. See the recommendation for more details.
If unit testing is focused on testing the tiny, essential bits of the functionality (isolated), the acceptance test do test the units in cooperation, as if it was real run of the system.