Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow test suite to wait for a length of time with no writes to the Node. #50

Open
nemanja-boric-sociomantic opened this issue Jun 1, 2018 · 5 comments

Comments

@nemanja-boric-sociomantic

Many applications are architectured in a way where some predefined input has been feed into them, process the input and output the profiles into, say, DHT. It's often necessary to know that the application has finished all processing and that all writes landed into the output node before confirming the contents of it.

One of the easiest ways, which may be just enough for most purposes is to allow turtle to wait for a length of time with no changes made to the whatever fake node.

@nemanja-boric-sociomantic
Copy link
Author

Removed the assigned milestone to let @mihails-strasuns-sociomantic assign it, if this ticket is valid.

@mihails-strasuns-sociomantic
Copy link
Contributor

One clarification - in this case expectRecordChange is not suitable because it is not known which record will change last?

@nemanja-boric-sociomantic
Copy link
Author

That's correct - the user may not know the last record. Am I right @jens-mueller-sociomantic ?

@jens-mueller-sociomantic
Copy link

jens-mueller-sociomantic commented Jun 5, 2018

Yes, you're right.
Note though, that it is currently unclear whether turtle is the way to go for my current use case. Maybe consult with others if they need/want this feature.

@mihails-strasuns-sociomantic
Copy link
Contributor

That would be indeed curious to hear. In general that sounds a bit out of line with turtle purpose (very fine-grained application testing) as one is expected to know somewhat precisely which records will change in what order - but practical demands are always different from theory :)

I will mark this as blocked for now and wait for more requests.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants