View Service - Testcase_Err_004 - Reflecting erroneous Nodes on GUI when affected with Bad_XXX status code|OPC Certification and Interoperability Testing|Forum|OPC Foundation

Avatar
Search
Forum Scope


Match



Forum Options



Minimum search word length is 3 characters - maximum search word length is 84 characters
Lost password?
sp_Feed sp_PrintTopic sp_TopicIcon
View Service - Testcase_Err_004 - Reflecting erroneous Nodes on GUI when affected with Bad_XXX status code
Avatar
Dipika Khera
Member
Members
Forum Posts: 52
Member Since:
11/15/2019
sp_UserOfflineSmall Offline
1
05/05/2020 - 09:00
sp_Permalink sp_Print sp_EditHistory

Hi Team,

There is one test case fromView Service Err-004. 

Description: ServiceResult = Good. BrowseResults are as follows: [0].StatusCode = Bad_NodeIdUnknown [1].StatusCode = Bad_NodeNotInView [2].StatusCode = Bad_NodeIdInvalid Any remaining results are unaltered.

Expected Result: Client reports the error. A graphical display would clearly reflect a problem with the affected nodes that were attempted to be browsed.

CTT script has description: Clears the results of a BrowseHelper call.

Actual Result: We have handled status codes, added logs for the same & restricting browse calls for affected Nodes. But, the test case also says, it should be displayed/reflected on GUI.

Is visualization on GUI necessary ? If yes, how should it is required to be done ? Why description in CTT script says Clear results of BrowseHelper Call ? I didn't find any BrowseHelper call in CTT trace, could you please elaborate a bit more about BrowseHelper call ?

Thank you

Avatar
Alexander Allmendinger
Germany
Moderator
Members

Moderators

Moderators-Specifications

Moderators-Companion

Moderators-Implementation

Moderators-Certification

Moderators-ProductsServices
Forum Posts: 67
Member Since:
07/11/2017
sp_UserOfflineSmall Offline
2
05/10/2020 - 10:57
sp_Permalink sp_Print

Dear Dipika,

the description in the script seems to be a copy-paste issue when the script has been created. Please enter a mantis issue for this so we can update the description in the script to reflect the actual test case description.

A visualization in the GUI is not required but recommended. But this visualization could also be an entry in a log pane of a browser. If something like this is not available, logging the errors in a log or trace is also allowed for passing the test case. The idea is, that an end users sees why he doesn't get the child nodes, because of an error. So he can try to solve the issue or point the problems out to the vendors.

Regards,
Alexander Allmendinger

Avatar
Dipika Khera
Member
Members
Forum Posts: 52
Member Since:
11/15/2019
sp_UserOfflineSmall Offline
3
05/11/2020 - 02:54
sp_Permalink sp_Print

Thank you Alexander for reply.

As suggested, I've raised Mantis Issue to update CTT test case description 0005637: Improve test case description in CTT - View Service - Err-004.

Forum Timezone: America/Phoenix
Most Users Ever Online: 510
Currently Online: Hiren Thakkar, Terje Kvangardsnes, Dave Cowley
Guest(s) 32
Currently Browsing this Page:
1 Guest(s)
Top Posters:
Forum Stats:
Groups: 2
Forums: 10
Topics: 1434
Posts: 4854