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

Question: Why is Update test not transactional? #326

Closed
robfig opened this issue Jun 5, 2013 · 4 comments
Closed

Question: Why is Update test not transactional? #326

robfig opened this issue Jun 5, 2013 · 4 comments

Comments

@robfig
Copy link
Contributor

robfig commented Jun 5, 2013

Out of curiosity, why is the Update test not required to be transactional? It seems like that makes it much less realistic -- I doubt that anyone is doing read-updates outside of a transaction in real life. And exercising the framework's transaction support seems like a good thing.

@bhauer
Copy link
Contributor

bhauer commented Jun 5, 2013

Hi @robfig. That's a great idea. I've added "Transactional update test" as a new test type on #133.

Rather than change test 5, I'd prefer to test transactions as a new kind of test. I'd welcome a draft mini-spec for the test. :)

@robfig
Copy link
Contributor Author

robfig commented Jun 6, 2013

Heh, not sure I have any ideas for it other than what the Update test is already. Do you have any thoughts?

@bhauer
Copy link
Contributor

bhauer commented Jun 6, 2013

@robfig Nothing in particular comes to mind, but I always like asking. Some really good ideas have come from the community. :)

@bhauer
Copy link
Contributor

bhauer commented Jun 6, 2013

I'm closing this since I have this captured as a new test type for the future.

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

No branches or pull requests

2 participants