Re: Unit Tests Behaving Oddly on new Session Id Storage feature

@Rob Following up: I think the issue is that jsdom v9 has no concept of sessionStorage, so when getInitialSettings runs, we have a complete failure of UserALE.js within the jsdom environment. This would affect .options and .log APIs. I haven’t pushed more work on this, just have done some

[jira] [Comment Edited] (FLAGON-451) Update unit tests to accommodate session storage features

[ https://issues.apache.org/jira/browse/FLAGON-451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16928203#comment-16928203 ] Joshua Poore edited comment on FLAGON-451 at 9/12/19 5:08 AM: -- [~rf] One

[jira] [Comment Edited] (FLAGON-451) Update unit tests to accommodate session storage features

[ https://issues.apache.org/jira/browse/FLAGON-451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16928203#comment-16928203 ] Joshua Poore edited comment on FLAGON-451 at 9/12/19 5:07 AM: -- [~rf] One

[jira] [Commented] (FLAGON-451) Update unit tests to accommodate session storage features

[ https://issues.apache.org/jira/browse/FLAGON-451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16928203#comment-16928203 ] Joshua Poore commented on FLAGON-451: - One likely cause for unit test failure owing to sessionStorage

[jira] [Commented] (FLAGON-441) utilize sessionStorage for sessionId so that sessionId isn't cleared until the tab is closed.

[ https://issues.apache.org/jira/browse/FLAGON-441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16928196#comment-16928196 ] Joshua Poore commented on FLAGON-441: - moving conversation to