Welcome to mirror list, hosted at ThFree Co, Russian Federation.

github.com/Ultimaker/Cura.git - Unnamed repository; edit this file 'description' to name the repository.
summaryrefslogtreecommitdiff
path: root/tests
AgeCommit message (Collapse)Author
2022-07-08Use optional assert message instead of printJaime van Kessel
2022-07-08Fix buildvolume testsJaime van Kessel
2022-07-08Fix Convex hull decorator testsJaime van Kessel
2022-03-28Merge branch 'master' into CURA-8640_PyQt6Jelle Spijker
# Conflicts: # cura/UI/CuraSplashScreen.py
2022-03-24Remove old arranger codeJaime van Kessel
Major vesion upgrade, time to clean some stuff up! CURA-7810
2022-03-24Merge branch 'master' into CURA-8640_PyQt6Jelle Spijker
# Conflicts: # cura/CuraApplication.py # resources/qml/Preferences/Materials/MaterialsSyncDialog.qml # resources/qml/Preferences/Materials/MaterialsView.qml
2022-02-21Merge branch 'master' into PyQt6_upgradeGhostkeeper
Conflicts: cura/PlatformPhysics.py -> Removed shapely on master, while QTimer import got updated to Qt6. plugins/Toolbox -> Entire folder is deleted in master, but it was updated to Qt6 here. This can all be removed.
2022-02-11fix inclusion of brim_gap in TestBuildVolumefix_disallowed_brim_gap_distanceTim Kuipers
2022-02-08Add testing for raft_surface_layersj.delarago
CURA-8915
2022-02-03Test multiple raft interface layersGhostkeeper
Should arrive at the correct raft thickness too then. Contributes to issue CURA-8915.
2022-01-12Add more settings for test of build volume limitsGhostkeeper
These new settings are necessary or the test will get exceptions that these settings don't exist. Contributes to issue CURA-8868.
2021-12-29Qt5->Qt6: More renamed stuff.Remco Burema
part of CURA-8591
2021-12-28Search/replace Qt5->Qt6.Remco Burema
part of upgrading Qt to v6.2: CURA-8591
2021-12-15Fix build-volume (related) tests.Remco Burema
part of CURA-8083
2021-11-22Remove unnecessary importGhostkeeper
We're not using this library any more now. Not even in the tests. Contributes to issue CURA-8539.
2021-11-22Remove tests checking for data in UserProfileGhostkeeper
The UserProfile is being stored in the account with a simple assignment, and these are just some property getters with a fallback. I don't think we need to test that. The actual getting of a user profile (and whether that returns correctly when logged out and such) is already tested as part of the OAuth flow where that code lives. Contributes to issue CURA-8539.
2021-11-22Fix assertion of resulting profile via callbackGhostkeeper
Needs to work differently with the asynchronous workflow. Contributes to issue CURA-8539.
2021-11-22Fix patching of getUserProfileGhostkeeper
The actual profile is not necessary for this test. But this function always returns None and we shouldn't patch it to make it return something else. Contributes to issue CURA-8539.
2021-11-22Fix checking return values in log-in/log-out flow testGhostkeeper
Contributes to issue CURA-8539.
2021-11-22Remove test simulating request error in user profileGhostkeeper
We're no longer generating that error. We're generating a QNetworkReply with a built-in error code and those errors are handled the same way as the failed requests tested above. Contributes to issue CURA-8539.
2021-11-22Fix test checking for failure of refresh token to reset authGhostkeeper
It was previously mocking some return values that should now get returned via callbacks. And it was previously relying on a web service which might not connect at all. Contributes to issue CURA-8539.
2021-11-22Also mock POST command and a failed responseGhostkeeper
Otherwise it'll end up using actual internet connections anyway. Not what we want. Contributes to issue CURA-8539.
2021-11-22Simulate an actual expired authentication tokenGhostkeeper
The test should trigger the refresh token to be used to get a new authentication token. Contributes to issue CURA-8539.
2021-11-22Mock HttpRequestManager getting the profile with refresh tokenGhostkeeper
I'm not sure the refresh token is actually used though. I might want to try to guarantee that. Contributes to issue CURA-8539.
2021-11-22Rewrite test to mock HttpRequestManager with authentication failureGhostkeeper
That's the expected outcome of the premise of this test. Contributes to issue CURA-8539.
2021-11-22Actually mock a reply from the auth serverGhostkeeper
The reply is not really relevant. The reply is mocked through readJSON. So it turns out that so far, our tests have been making actual requests to the authentication server, and depended on it being online. Not good. Mock those external dependencies! Contributes to issue CURA-8539.
2021-11-22Use docstring format for this documentationGhostkeeper
Contributes to issue CURA-8539.
2021-11-22Test for result of callback with a callableGhostkeeper
In this case the callback should get called immediately (no wait) so it is safe to test for this callback, albeit slightly implementation-defined. Contributes to issue CURA-8539.
2021-10-13Patch CuraApplication away while running tests for output devicesGhostkeeper
It needs CuraApplication because it wants to set metadata on the printer. But this is not relevant for the tests. Contributes to issue CURA-8609.
2021-09-08Fix typo in file nameJaime van Kessel
CURA-8544
2021-09-07Fix source typosluz paz
2021-09-07Fix various typosluz paz
Found via `codespell -q 3 -S *.po,*.pot -L childs,initialy,lod,ned,te,slicable,sur,tutoriels,wont`
2021-08-31Add test to see if all deprecated theme icons still existGhostkeeper
This will make it easier in the future if we deprecate icons again. And it's nice for now. Contributes to issue CURA-8520.
2021-08-09Fix failing testKonstantinos Karmas
CURA-8441
2021-05-10Remove unneeded pycapsule importsJaime van Kessel
2021-04-28Merge branch 'fix_group_rename' of https://github.com/fieldOfView/CuraJaime van Kessel
2021-04-26Fix test_wrongServerResponsesGabriel FĂ©ron
2021-04-20Fix ObjectsModel test to allow non-autogenerated group-namefieldOfView
2021-03-08Add test to ensure that no definitions define new settingsGhostkeeper
See the documentation of the test.
2020-12-18Fix testsJaime van Kessel
CURA-7835
2020-11-10Fix assertionKostas Karmas
CURA-7833
2020-11-10Add tests for correctPrintSequenceKostas Karmas
CURA-7833
2020-11-10Merge branch '4.8'Remco Burema
2020-11-09Remove outdated testsKostas Karmas
CURA-7827
2020-11-06Patch the updateNumberExtrudersEnabled temporarilyKostas Karmas
CURA-7827
2020-11-06Add tests for _correctPrintSequenceKostas Karmas
CURA-7827
2020-11-06Fix failing tests in TestMachineManagerKostas Karmas
When the machine manager calls the _onGlobalContainerChanged(), it calls updateNumberExtruders Enabled, which triggers the signal numberExtrudersEnabledChanged. This, in turn, triggers the need to check the MachineManager's pyqtProperty numberExtrudersEnabled. Now, since this property has no setter, it cannot be patched. Instead, to work properly, patch the updateNumberExtrudersEnabled. CURA-7827
2020-10-30Skip running the tests for the old arrange algorithmKostas Karmas
So that the output of the CI/CD testing step is not cluttered with deprecation warnings. Done during TTT
2020-10-16More fixes for PyCapsule_GetPointer race conditionGhostkeeper
One of the weirdest errors out there, and as far as I know we're the only ones suffering from it, due to having multiple packages of Python bindings created with Sip as well as having PyQt and different threads.
2020-10-16Fix PyCapsule_GetPointer error when running testsGhostkeeper
This obscure error happens when a module with Sip bindings is being imported after PyQt. Due to a clash with the Sip versions or something, it then fails on the custom module. Import all of our custom modules with Sip bindings first.