TimeStamp::ok()
Since all getTimeStamp are not returning a boolean of success, some wrong TimeStamp should be defined to allow getters to provide a "wrong" output. Now it is 0. But it is used in many tests. Maybe it is still ok. Let's discuss it.
Since all getTimeStamp are not returning a boolean of success, some wrong TimeStamp should be defined to allow getters to provide a "wrong" output. Now it is 0. But it is used in many tests. Maybe it is still ok. Let's discuss it.