Hi Team,
The following error log is displayed in ServiceCenter when BDDFramework is executed from "CI/CD Probe".
Error log: "Object reference not set to an instance of an object.
After investigating the error location, it seems that the error occurs in "REST->v1->ScanBDDTestEndpoints".
I can't figure out how to deal with this error message.
What we have confirmed.
1. the error occurred when using BDDFramework from Jenkins.
However, it also occurred with "CI/CD Probe" alone.
2. We also checked the Extensions log, and found that "Xml.XmlElement_GetAttributeValue.
XmlElement_GetAttributeValue", the same error as in the "CI/CD Probe" error log occurred.
3. The Json file of the screen list, which is the subsequent process, could be obtained.
I'd appreciate your advice if you are familiar with this matter.
Best,
Hi Ota-san,
I'm not a member of the team, but I had a similar experience in the past.
So, I'd like to share it.
The stack trace in the screen shot shows that the error occurred in an action of "OutDoc" component.
(ScanBDDTestEndpoints API uses the Section_3_2_GenerateWebScreen action of OutDoc to retrieve test cases from the module)
This component uses a bit older version of OutDoc, which may cause errors when used for modules created with newer versions of OutSystems.
Can you try updating OutDoc module and the reference of CI/CD probe?
In my environment, the problem occurred was solved by updating the module.
But if what you wrote in 3 means that ScanBDDTestEndpoints is correctly returning the screen list, it might be different.
Hi Watanabesan,
Thank you for your response.
The error still occurred in my environment even after everything was up to date.
It seems that there is a Null screen in the screen list and the error occurs.
I wonder if something has changed...
By the way, do you remember what version you were using when you solved the problem?
Please let me know if you remember.
Regards,
It was the same version of the current one: v 2.1.0
I don't remember the exact version of OutDoc. However it was a few months ago, so it can't be that old version.
By the way, there is another discussion related to this one: [CI/CD Probe] Why am I having "Object reference not set to an instance of an object." error?
It seems like the same symptom by looking at the stack trace. This one is marked as solved because there is little actual harm.
Is the problem you are having the same as this one?
Sorry for the late reply.
Thanks for the info on the version.
I have already checked the link you gave me and it is probably the same as this one, but I have no proof.
I really hope there isn't a problem...
I'll wait to hear back from the creator!