-
-
Notifications
You must be signed in to change notification settings - Fork 15
Unit-test-- ensure data is a particular number of hours. #164
Copy link
Copy link
Open
Labels
dataAnything related to databases, data management, stuff that is heavily focused in the data directory.Anything related to databases, data management, stuff that is heavily focused in the data directory.low priorityIssues we are not currently focusing on, either because it has a lot of blockers or isn't important.Issues we are not currently focusing on, either because it has a lot of blockers or isn't important.testingAdding unit-tests and integration tests.Adding unit-tests and integration tests.
Metadata
Metadata
Assignees
Labels
dataAnything related to databases, data management, stuff that is heavily focused in the data directory.Anything related to databases, data management, stuff that is heavily focused in the data directory.low priorityIssues we are not currently focusing on, either because it has a lot of blockers or isn't important.Issues we are not currently focusing on, either because it has a lot of blockers or isn't important.testingAdding unit-tests and integration tests.Adding unit-tests and integration tests.
Basically this issue falls into two parts.
First, make sure the hours limitation works. It has pretty predictable behavior:
This is based on live data, not the mock data.
That's the second part of this issue. I currently have 1 test that uses live data, and the rest can use mock data. Am I doing a good job at isolating the two categories of tests? There might be a better way of doing this than what I'm currently doing. Need to look into that.