Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Implement support for proxying pages inside ASAR archives #2033

Closed
AndreyBelym opened this issue May 28, 2019 · 1 comment
Closed

Implement support for proxying pages inside ASAR archives #2033

AndreyBelym opened this issue May 28, 2019 · 1 comment
Assignees
@Farfurix
Labels
AREA: server !IMPORTANT! STATE: Auto-locked Issues that were automatically locked by the Lock bot SYSTEM: pipeline TYPE: enhancement
Milestone
Sprint #37

Comments

@AndreyBelym
Copy link
Contributor

It's very common for Electron apps to ship their resources (including pages) inside ASAR archives. Since Hammerhead can't read packed files, it leads to difficulties in testing builded Electron apps. We can modify the FileRequest class to use the electron/asar module to reads an archived content on the fly and provide it to the browser under test.
@AndreyBelym AndreyBelym changed the title Implement support for proxying pages inside ASAR archives. Implement support for proxying pages inside ASAR archives May 28, 2019
@AndreyBelym AndreyBelym added this to the Sprint #34 milestone May 28, 2019
@aleks-pro aleks-pro mentioned this issue Jun 5, 2019
Closed
@Farfurix Farfurix mentioned this issue Jun 12, 2019
Merged
@LavrovArtem LavrovArtem modified the milestones: Sprint #34, Sprint #35 Jun 17, 2019
@Farfurix Farfurix mentioned this issue Jun 17, 2019
Merged
@LavrovArtem LavrovArtem modified the milestones: Sprint #35, Sprint #36 Jul 3, 2019
@LavrovArtem LavrovArtem modified the milestones: Sprint #36, Sprint #37 Jul 17, 2019
@lock
Copy link

lock bot commented Aug 4, 2019

This thread has been automatically locked since it is closed and there has not been any recent activity. Please open a new issue for related bugs or feature requests. We recommend you ask TestCafe API, usage and configuration inquiries on StackOverflow.

@lock lock bot added the STATE: Auto-locked Issues that were automatically locked by the Lock bot label Aug 4, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Aug 4, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@Farfurix Farfurix

Labels
AREA: server !IMPORTANT! STATE: Auto-locked Issues that were automatically locked by the Lock bot SYSTEM: pipeline TYPE: enhancement
Projects
None yet
Milestone
Sprint #37
Development

No branches or pull requests
3 participants
@AndreyBelym @LavrovArtem @Farfurix