healenium / healenium-backend

Client for Healenium
Apache License 2.0
23 stars 26 forks source link

discrepancies in healing report table and healing_result table in postgres database #40

Open naveenkmr2310 opened 3 years ago

naveenkmr2310 commented 3 years ago

Hi Team, After Successful healing and connecting to db to view the results, we observed extra locator being add to the healing_result table post run. While generating the report after 'mvn clean test', we are observing that the records in the report table in empty until we do the next execution with healing. We also observed the records remains empty even after trying 'mvn clean test' multiple times.


Below picture the of healing_result db. Entries 44,45, 47 and 48 are additional entries added to the db which wasn't healed.

image


Below is the screenshot of reports table, the reports record is empty as shown in first entry untill next execution with healing is done

image

Alex-Reif commented 3 years ago

Hello @naveenkmr2310 ,

Do you have opportunity to share your project ? It'll help to investigate the issue.

You can contact with me through email

naveenkmr2310 commented 3 years ago

Hi Aliaksei,

Since its confidential, we wont be able to share our project. We have configured healenium 3.1.4 as mentioned, the healing is happening successfully and also report is being generated with db data after maven clean test. But there are discrepancies in results like the records in the report table is empty until we do the next execution with healing. We are blocked here and not able to proceed with healing results handling due to this unusual pattern. Kindly provide some insights regarding the issue. Also share your email address or you can contact me on naveen.s@valuelabs.com for further communication.

Thank you!!

naveenkmr2310 commented 2 years ago

Hi Aliaksei, Any updates on the above issue? Kindly take a look into the issue and provide some insights. Thank you!!