Skip to content

[Backend] - Names for assignments - #455

Merged
thomasdejaeghere merged 5 commits into
developmentfrom
417-names-for-assignments-2
Apr 21, 2025
Merged

[Backend] - Names for assignments#455
thomasdejaeghere merged 5 commits into
developmentfrom
417-names-for-assignments-2

Conversation

@brieromb

Copy link
Copy Markdown
Contributor

made the change for names in assignments on another branch again, because I thought that I did something wrong in solving the many merge conflicts on the other branch.

@brieromb brieromb added enhancement New feature or request backend labels Apr 17, 2025
@brieromb brieromb added this to the Milestone 2 milestone Apr 17, 2025
@brieromb brieromb self-assigned this Apr 17, 2025
@brieromb brieromb changed the title Names for assignments [Backend] - Names for assignments Apr 17, 2025
@brieromb

Copy link
Copy Markdown
Contributor Author

@thomasdejaeghere There are still some integration tests that fail, but it's difficult to see which ones fail because the output of the failing tests is removed from my terminal because there is so much output from all the tests after them. How can I properly this?

@bramcomyn

Copy link
Copy Markdown
Contributor

@thomasdejaeghere There are still some integration tests that fail, but it's difficult to see which ones fail because the output of the failing tests is removed from my terminal because there is so much output from all the tests after them. How can I properly this?

You can always redirect output to a logfile

command > output.txt

after which you can view the output through tools like less

less output.txt

I would suggest pulling the latest changes from development onto your branch, as we wouldn't have merged the integration testing without all tests succeeding.

@bramcomyn

Copy link
Copy Markdown
Contributor

Also @brieromb, you can just check the logs in the backend workflow, which also shows the failing tests. It might give you a first idea.

@bramcomyn

Copy link
Copy Markdown
Contributor

And as a last comment so far, @brieromb, could it be that the integration tests fail because they were based on an assignment which doesn't have a name field? Could it be that this breaks the server? I feel like it would reasonably be your responsibility to update them.

@thomasdejaeghere

Copy link
Copy Markdown
Contributor

And as a last comment so far, @brieromb, could it be that the integration tests fail because they were based on an assignment which doesn't have a name field? Could it be that this breaks the server? I feel like it would reasonably be your responsibility to update them.

Yes @bramcomyn I tested on @brieromb his branch and that is indeed the case, the assignment objects and comparison objects in tests need to be updated with the extra field.

@brieromb

Copy link
Copy Markdown
Contributor Author

All tests now pass.

The problem did not lie in the tests, but elsewhere.

The problem was that in the data source create assignment code, there was a hard coded conversion, instead of the createTypeORM method. I looked over that hard coded conversion initially, so that was not updated with the extra name field. but now I changed that to use the provided method for this.

@thomasdejaeghere
thomasdejaeghere merged commit a41fda8 into development Apr 21, 2025
@thomasdejaeghere
thomasdejaeghere deleted the 417-names-for-assignments-2 branch April 21, 2025 18:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backend enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants