matheusgr / easyaccept Goto Github PK

EastAccept should generate test scripts when a client is using the System under Test (SUT). EasyAccept should capture clients actions and record those actions in a "easyaccept script format". The generated script should used to repeat the same test.

The print command should simply execute a command and prints the returned result.

In EasyAccept scripts we should pass collections of strings as parameters.
According (for example) to the following syntax: command param={ abc, "def, ghi", "{"}

Make using beans easy in easyaccept (as parameters, return values, script variables, etc.)
In other words, there are advantages to having a façade deal with beans and not only native data
since many modelues such as JSP, etc. can interface to a facade easier by dealing with beans
This should be available as return values, parameters, script variables, ...

Possible syntax
expect "John Doe" getStudent.name id=${id1}
student=getStudent id=${id1}
expect "John Doe" ${student}.name

Allow user to define a custom log format.

In the current implementation, a command can only return a simple string.

A command should return a collection of strings, the expected string
should have the syntax {"John Doe","Mary Stuart"}

Where s1 is the string representing the first object in the collection, etc.

Since EasyAccept expected results with actual results, the collections (a clss that implements Java Collection interface) returned by Facade methods should be converted to this same syntax (or vice-versa), to allow the comparison between "expected results" and "returned results".

For example:
expect {"John Doe","Mary Stuart"} getUserNames age=20

In this case, the getUserNames command returns a collection.

When Easyaccept calls a method from a Facade and this method throws an unexpected exception, EasyAccept does not report were the exception had ocurred.

ex:
Command: <rollDice firstDieResult="1"(java.lang.Byte)
secondDieResult="1"(java.lang.Byte)>, produced error: <This place can't be sold>

EasyAccept should show the line of code where this excetion had ocurred
(and ,possibly, he line of scritp test that generates this error).