Sign up to take part
Registered users can ask their own questions, contribute to discussions, and be part of the Community!
Fixed copy of Python-based scenario that did not copy the script
Added on December 4, 2024 5:58PM
Likes: 0
Replies: 4
Trinath
Registered Posts: 3 ✭✭✭
How can we effectively replicate this issue in order to conduct thorough testing during the version upgrade process? Specifically, what steps should we follow to ensure that the issue is accurately reproduced, and what testing methodologies can we apply to assess its impact in the new version?
Operating system used: Windows
Operating system used: Windows
Answers
-
Turribeach Dataiku DSS Core Designer, Neuron, Dataiku DSS Adv Designer, Registered, Neuron 2023 Posts: 2,409 NeuronI don’t really understand your issue. You had a “Python scenario script that didn’t copy”. Didn’t copy for where to where? Explain exactly what you did and what was the result.
-
Please find the details in the release nots 12
-
I am uncertain about the nature of the fix implemented by the Datiku team, and the brief details provided in the release notes do not contain any comprehensive information.
-
Turribeach Dataiku DSS Core Designer, Neuron, Dataiku DSS Adv Designer, Registered, Neuron 2023 Posts: 2,409 Neuron
It's not really your job to test bug fixes, that's Dataiku's job. Trying to replicate bugs that don't affect you doesn't sound like a reasonable strategy. Dataiku usually does 2 releases a month with dozens of bug fixes in every release the majority of which you are unlikely to be impacted by. In terms of functional testing I would only recommend testing fixes that you are actually impacted by in which case you should know well what are the conditions for the bug to be reproduced. The rest of your focus should be on testing your flows/scenearios/jobs run well in the new version.
