-
Notifications
You must be signed in to change notification settings - Fork 3
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
Ultra specific testing for debug purposes #1
Comments
I don't think this can be done with the current Would you want to run a test like this repeatedly? If it's just for debugging, you could check it pretty succinctly with a direct call to
Could you say more about the use cases you're thinking of, though? |
Fare, It was a thut I had at the end of the User Conference with you, and so I thout I'd start a conversation. |
The example above is general - that is, anyone using orca could construct a battery of tests of specific cells in a table using index locations -- but that might not be a very common use case for larger tables. If there are any specific examples it might help think about what functionality might be missing. |
So I have not thout this thrue. The thout came up as we were discussing debugging of a model. We were talking about the experience of looking at results of a long running model and wondering "where did that value come from." and just having come from the excellent orca_test talk, I was wondering if we could use it to get a breakpoint on the new value showing up. |
Can we assert the value for a specific cell of a table?
The text was updated successfully, but these errors were encountered: