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.

Sign up for GitHub

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

Jump to bottom

Bug: Not all ways to retrieve Test Data show up in the Report #360

Open
5 tasks
wurzelkuchen opened this issue Feb 13, 2025 · 0 comments · May be fixed by #361
Open
5 tasks

Bug: Not all ways to retrieve Test Data show up in the Report #360

wurzelkuchen opened this issue Feb 13, 2025 · 0 comments · May be fixed by #361
Assignees
@RobertAvemarg
Labels
bug codeReadyForMerge The issue was implemented and the branch is ready to be reviewed and merged into develop docsNeeded The documenttion needs to be checked if there are changes needed and if so, adaptions should be made
Milestone
v5.3.0

Comments

@wurzelkuchen
Copy link
Contributor

Quick Description

There are several ways to retrieve testdata inside Neodymium and not everything is covered by our testdata view.

Tasks

  • Unify the test data access inside one class which can be retrieved directly from our Neodymium.java
  • Make all DataUtils methods available inside this class
  • Old methods (e.g. DataUtils shall just wrap the new ones)
  • Mark methods which should not be used anymore (e.g. DataUtils, Neodymium.dataValue()) as deprecated and update the javadoc to point to the new methods)
  • Change the dataView Logic to always show the whole data set inside the report (for simplification)

Actual Behaviour

If I call Neodymium.dataValue() this is not put into the report.

Expected Behaviour

If I call any mehtod to retrieve test data, I want to see the test data inside the final report.
@wurzelkuchen wurzelkuchen added bug codeImplementationNeeded This issue requires a change in the code of Neodymium docsNeeded The documenttion needs to be checked if there are changes needed and if so, adaptions should be made labels Feb 13, 2025
@wurzelkuchen wurzelkuchen added codeReadyForRecheck The issue is fixed/implemented AND merged into development, but needs to be rechecked there and removed codeImplementationNeeded This issue requires a change in the code of Neodymium labels Feb 20, 2025
@wurzelkuchen wurzelkuchen added this to the v5.3.0 milestone Feb 20, 2025
@wurzelkuchen wurzelkuchen added codeReadyForMerge The issue was implemented and the branch is ready to be reviewed and merged into develop and removed codeReadyForRecheck The issue is fixed/implemented AND merged into development, but needs to be rechecked there labels Feb 20, 2025
@wurzelkuchen wurzelkuchen linked a pull request Feb 20, 2025 that will close this issue
360.add missing testdata to report #361
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@RobertAvemarg RobertAvemarg

Labels
bug codeReadyForMerge The issue was implemented and the branch is ready to be reviewed and merged into develop docsNeeded The documenttion needs to be checked if there are changes needed and if so, adaptions should be made
Projects
None yet
Milestone
v5.3.0
Development

Successfully merging a pull request may close this issue.

360.add missing testdata to report Xceptance/neodymium
2 participants
@wurzelkuchen @RobertAvemarg