-
Notifications
You must be signed in to change notification settings - Fork 18
Fixes for test conflicts #178
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
Conversation
did you try throwing in a |
|
Okay, all tests pass on ZTEST now, however there is a mysterious Alyx issue where the database sometimes returns a 500 for reasons we can't work out, however I think I've ironed out all of the client-side issues with the tests. |
tests/AlyxPanel_test.m
Outdated
| testCase.Panel.login('test_user', 'TapetesBloc18'); | ||
| testCase.fatalAssertTrue(testCase.Panel.AlyxInstance.IsLoggedIn,... | ||
| 'Failed to log into Alyx'); | ||
| testCase.fatalAssertEqual(testCase.Panel.AlyxInstance.BaseURL, BaseURLTestSetup,... |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@k1o0 I sent you some slack messages about this. This fails.
jkbhagatio
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
base url in AlyxPanel_test sometimes does not get appropriately set to 'testDev', causing some methods to fail (see slack messages)
Use DELETE to test both creating new session and viewingLines 233 to 237 in 829cac5
This comment was generated by todo based on a
|
Undoing your change fixed this and now the url is recorded without needing a test param
|
Should be good to go |
Hm, so the issue is that |
|
I don't think MATLAB throws a fit. If your param is in the setup block and you try to call a test method with it the test runner just removes those tests and throws a warning as you originally pointed out. What you did to try to fix it was just wrong: the values of properties in the setup and test blocks are independent of one another. A further error was caused by issue #180. My laptop was not fast enough to encounter these errors but ZTEST was. Now all tests appear to work reliably. |
I just checked and this still errors on 2017B... I don't follow...I know they're independent of one another. Can you elaborate? |
|
You mean the tests as they are on this commit cause an error on 2017b? Can you open an issue an attach the command output so I can look at the error? |
|
the issue is exactly as I've said in an above comment. Here is the output - I'm not sure it's worth an issue: I guess we should always run tests on 2018B or later? And in regards to this I did this in fact because they are independent of another, so I think you may have misunderstood my reason for doing so? |
|
I removed the BaseURL from test_activeFlag (d6b7def#diff-7edecec6036e5be04c667344842875f5R490) but missed the other two methods. I didn't realize because it doesn't cause an error on 2018 however the documentation indicates that they shouldn't be accessible to the test methods. I'll push a fix for this. Next time we Skype I'll go over how the AlyxPanel test works and why your fix failed. |
|
Done in #183 |
yeah, this is what I was looking for : ) Sure, I just wanted you to be aware that I knew my "fix" wasn't proper |
* Fixes for test conflicts * Ensure path is reset * Issue #180 * a fix to AlyxPanel_test/setupPanel, but still failing * Reverted some changes and added fix for activeFlag test * Bug fixes and updates for update to test db * Changes to alyx-matlab * Fix to recordWeight test * Fix for db bug cause submodule test fail
* Fixes for test conflicts * Ensure path is reset * Issue #180 * a fix to AlyxPanel_test/setupPanel, but still failing * Reverted some changes and added fix for activeFlag test * Bug fixes and updates for update to test db * Changes to alyx-matlab * Fix to recordWeight test * Fix for db bug cause submodule test fail
I've fixed the conflicts between the database tests and they all pass on my laptop. Frustratingly, these very same tests fail on ZTEST. I looked at
dat_testand it passes when I step through or set breakpoints (even conditional ones) but fails otherwise (but not always). I have a feeling thatsaveis asynchronous and so on faster machines it loads the paths before the custom paths file has finished saving. I'm not sure what the best way of getting around this is. Let me know how these tests run on the rigs.