- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
Onto the testing portion. Now that we have the setup done, here's how the flow runs stacked up. This was done by just triggering the main flow to generate a new date/time then compare that Flow Variable one by one against the values returned by the action. The first testing pass through was a disaster. Only Date 1 and 6 successfully completed a comparison, and the comparison on Date 6 didn't evaluate properly:
Date 1 - Type: Date
Date 6 - Type: Integer Date
The compares for Dates 2-5 came back with comparison issues either for parsing the value that was returned or a mismatch in the types that were being compared.
Date 2 - Type: Basic Date/Time
Date 3 - Type: Date/Time
Date 4 - Type: Other Date
Date 5 - Type: Due Date
However, the follow-up test was the fix for all of these problems. It was adding the toString() function to each output variable in the Action:
Doing that produced successful results across the board.
So the results of this test were that casting the date values out of the Action as strings allowed all the tests to process successfully and seemed to override whatever type the output variable was set to. It even fixed the test for date 6 which flipped the result from false to true.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.