search

maciejmaciejewski / azure-pipelines-protractor

Embed Protractor HTML report in Azure Pipelines
MIT License
3 stars 3 forks source link

ISSUE PUBLISHING PROTRACTOR REPORT #8

Open ybc9959 opened 4 years ago

ybc9959 commented 4 years ago

Hi, I have identified a issue. Don't know if I'm right.

In the previous version which *says 2.0 The log says only #vso processed for combine.json and no Screenshots are processed there, but it used to publish/show the Protractor report when we hit the Protractor Tab in Azure with no screenshots in it. Now From Friday, After the commit you made it is generating the #vso screenshots.png in the log & Successfully generating the Combine.json file but It is unable to load/Publish protractor report in Azure saying Failed to Load.** screenshots processiong version1 version1setup

6

maciejmaciejewski commented 4 years ago

Hello @ybc9959 Please contact me via email an we will debug the issue

ybc9959 commented 4 years ago

Upon checking this Extension, I had clearly figured out the error. -->Protractor Extension will Successfully process Images when they are in screenshots sub folder - But Protractor Fails saying Failed to Load Protractor Report (Whenever the images are processed in Log file - Protractor Report Fails to Load) --> Taking out the Screenshots Sub Folder / If the Automation Suite has no failures (No Screenshots) , then No images will be processed in the Log File - Protractor Successfully displays the Report

There is a problem in Extension File - When Images are Processed Report Completely Fails & When there is no Images in the Automation or disable Screenshots or Comment out the Screenshot Sub folder - Protractor Report Loads Successfully. [Html Report in the Physical Location Displays Images and everything Correctly, No mater If they are in sub folder or not. The Problem is combined.json file going to extension and I don't know how it is being converted]

ybc9959 commented 4 years ago

Screenshot (66)

maciejmaciejewski commented 4 years ago

Hey @ybc9959 Thanks for reaching out. I have a feeling that this might be due to some special characters in combined.json. Would you be able to run this on linux base agent?