In ATF once After completing test if i check the Screenshots i can see the black screen
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-15-2024 03:14 AM
Hi,
In ATF once After completing test if i check the Screenshots i can see the black screen.
I am using the Vancouver version.
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-15-2024 03:25 AM
Hello,
This is a known issue in the Vancouver Version and was later fixed.
Mentioned in below documentation (search with keyword black).
Please update the instance to the newest Vancouver Patch.
If my answer has helped you in any way please mark it as correct or helpful.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-15-2024 03:33 AM
Thanks for the response, But this error screenshot is coming only for one ATF only i have created almost 6 ATF's today all does able to open the screenshot and only for this ATF only i am getting the error.
Could you please address the issue.
Thanks,
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-15-2024 03:35 AM
But my test has only 6 test steps and i am not running in the Mozilla/Safari.
I am running the steps only in the Google chrome.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-15-2024 04:33 AM
Hi @kranthi2
Could you please share the test steps.
We were experiencing blank ATF screenshots on our Rome instance.
We had recently set the property for full screenshots, and it worked on some of our ATF tests, but on some we were seeing a black screen or a black screen with an empty white box in the middle. I saw this post, but there was no resolution. I found a support article that appears to have resolved the issue in our instance - KB1002214 , KB0963743 .
I set the property for sn_atf.screenshots.use_glide_screenshot to true per the related KB, and it resolved the issue for us.
I hope you find this helpful as well.
Regards
Shaqeel
***********************************************************************************************************************
If my response proves useful, please indicate its helpfulness by selecting "Accept as Solution" and " Helpful." This action benefits both the community and me.
***********************************************************************************************************************
Regards
Shaqeel