...
- The amount to be paid = (hours + minutes worked) * hourly rate
- The check in time and check out time must be specified. These times must be specified in the following format HH:MM [<AM|PM>], if AM|PM are not specified AM is assumed, otherwise 24hr notation may be used or any combination.
- The hourly rate is a decimal value
- The hours worked should be as a decimal value
You will not be responsible for the extrating of the data from the legacy system only the correcting and formatting of the times and, calculating the hours worked and how much they should be paid
Acceptance Criteria Statements
...
That's a really difficult question to answer. But let me try! I would start by saying the criticality of the application would be a major driver. I'm going to divide the world into two groups criticality and complexity. I'm using criticality as a measure of importance and value to the organization. I'm using complexity as a measure of how difficult it will be to implement/realize the use case/story for which the scenarios are related.Drawio
How to read the graph
Each quadrant represents a level a complexity and criticality.
...
| Drawio | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Create a your FitNesse wiki page
Begin by creating your first wiki page (follow the instructions on fitnesse.org on how to create a sub-page of the home page of the wiki). In this new page add the following wiki markup text
| Code Block | ||||||
|---|---|---|---|---|---|---|
| ||||||
!contents -R2 -g -p -f -h
#!define COMMAND_PATTERN {java -Xdebug -Xrunjdwp:transport=dt_socket,server=y,suspend=y,address=1044 -cp %p %m}
!define TEST_SYSTEM {slim}
!*> '''Classpath'''
${maven.classpath}
*!
!path C:\work\software\netbeans\tdd_with_fitnesse_v2\dist\tdd_with_fitnesse_v2.jar
|import |
|tdd_with_fitnesse|
!|TimeSheet |
|Check In Time|Check Out Time|Hourly Rate|Check In Time Normalized?|Check Out Time Normalized?|Hours Worked?|Pay? |
|9:00 AM |5:00 PM |7 |09:00 |17:00 |8.00 |56.00|
|10:30 AM |12:30PM |4 |10:30 |12:30 |2.00 |8.00 |
|9:45AM |12:45 PM |10 |09:45 |12:45 |3.00 |30.00|
|9:30 AM |12:15 |10 |09:30 |12:15 |2.75 |27.50|
|09:30 |12:15 PM |10 |09:30 |12:15 |2.75 |27.50|
|9:00 AM |15:00 |8 |09:00 |15:00 |6.00 |48.00|
|09:00 |3:00 PM |8 |09:00 |15:00 |6.00 |48.00|
|9:05 PM |3:30 PM |7 |21:05 |15:30 |ERR |NIL |
|13:05 AM |4:30 PM |7 |ERR |16:30 |0.00 |0.00 |
|08:59 |09:01 |8 |08:59 |09:01 | | |
|
Lines 5 - 7: specify the path where the classes can be found if you are doing a maven build
Line 8: specifies the path where the jar file can be located if you want to be explicit about the target to be tested
Line 11: specifies that you are going to indicate the namespace (packages in Java, namespace in .net, namespace in C++) where the SUT can be found
Line 12: the package/namespace name
Line 14: the fixture class name
Line 15: the parameter field names, no question mark 
represents an input field, a field name followed by a question mark represents an output field
...