createing a dataset for PersonalServiceTest class

[josephbate]

Pull Requests Requirements

• The PR title includes a brief description of the work done, including the
  Issue number if applicable.
• The PR includes a video showing the changes for the work done.
• The PR title follows conventional commit label standards.
• The changes confirm to the OpenElis Global x3 Styleguide and design
  documentation.
• The changes include tests or are validated by existing tests.
• I have read and agree to the Contributing Guidelines of this project.

Summary

created a person.xml to preload data in the test enviroment to be used for testing

• however @mozzy11 @mherman22 i have follow quite som challenges making CRUD test operation on this service since inheriting the dbunit library
• methods like create person, update person and delete person (which are commented out) tend to give off errors and exceptions as seen in the logs; https://pastebin.com/bQ3KtRi2, https://pastebin.com/fKAAH5Bj,
• the insert /save method for some reason assigns any intial saved person with id "2" as a default generated id, each time you try to create a person. thus this lead to duplication which brings the persitance to a halt. that simply means that if we pre-load data in the test environment we cannot Test CRUD methods against the service in this case personService

i also faced an another challenge with the createPersonWithMultiplePatients_shouldLinkPatientsToPerson() since crud is a bit of a challenge we cannot create a person to assign patient so i tried assigning from the data set but that seem also a challenge here are the error logs; https://pastebin.com/GBfFnqVy

@mozzy11 @mherman22 please do advise on this issue
thank you

Screenshots

[Add relevant screenshots here if applicable]

Related Issue

[Add a link to the related issue or mention it here if applicable]

Other

[Add any additional information or notes here]

[mherman22]

@josephbate uncomment the commented stuff so that we can see the behaviour on ci. Also fix fomatting

[mherman22]

the insert /save method for some reason assigns any intial saved person with id "2" as a default generated id, each time you try to create a person. thus this lead to duplication which brings the persitance to a halt. that simply means that if we pre-load data in the test environment we cannot Test CRUD methods against the service in this case personService

we need to create a resetSequence method that connects to the database using a DataSource and queries for the maximum value of a specified column in a table. Then, use the PostgreSQL setval function to update the sequence to maxId + 1, ensuring the sequence aligns with existing data. This has alot to do with how OpenELIS handles ID generation using a custom StringSequenceGenerator that generates and then converts the Long ID to StringFormat.

The StringSequenceGenerator generates numeric IDs but formats them as strings, and when records are deleted or modified, the sequence might fall out of sync with the actual maximum ID value in the table.

cc: @josephbate @mozzy11

[mherman22]

the insert /save method for some reason assigns any intial saved person with id "2" as a default generated id, each time you try to create a person. thus this lead to duplication which brings the persitance to a halt. that simply means that if we pre-load data in the test environment we cannot Test CRUD methods against the service in this case personService

we need to create a resetSequence method that connects to the database using a DataSource and queries for the maximum value of a specified column in a table. Then, use the PostgreSQL setval function to update the sequence to maxId + 1, ensuring the sequence aligns with existing data. This has alot to do with how OpenELIS handles ID generation using a custom StringSequenceGenerator that generates and then converts the Long ID to StringFormat.

The StringSequenceGenerator generates numeric IDs but formats them as strings, and when records are deleted or modified, the sequence might fall out of sync with the actual maximum ID value in the table.

cc: @josephbate @mozzy11

@josephbate did you get anywhere with this? Or found a better solution than this?

[josephbate]

the insert /save method for some reason assigns any intial saved person with id "2" as a default generated id, each time you try to create a person. thus this lead to duplication which brings the persitance to a halt. that simply means that if we pre-load data in the test environment we cannot Test CRUD methods against the service in this case personService

we need to create a resetSequence method that connects to the database using a DataSource and queries for the maximum value of a specified column in a table. Then, use the PostgreSQL setval function to update the sequence to maxId + 1, ensuring the sequence aligns with existing data. This has alot to do with how OpenELIS handles ID generation using a custom StringSequenceGenerator that generates and then converts the Long ID to StringFormat.
The StringSequenceGenerator generates numeric IDs but formats them as strings, and when records are deleted or modified, the sequence might fall out of sync with the actual maximum ID value in the table.
cc: @josephbate @mozzy11

@josephbate did you get anywhere with this? Or found a better solution than this?

yes i did and this worked
however i am still debugging the the issue of the unit test of the createPersonWithMultiplePatients_shouldLinkPatientsToPerson()
tried editing the restoreDatabase()

[josephbate]

• The test case did not report any output.
• The test case did not report any output.
• The test case did not report any output.
• The test case did not report any output.

[mherman22]

Great work on this. Will find time and take a look at this. Keep grinding