BUG-1: Jest Testing Failing on ES6 Imports

[RGPosadas]

Bug Description

Jest fails when it sees an import on ES6 assets.

Steps To Reproduce The Bug

> npm test

What Is The Expected Result?

Jest passes the test.

What Is The Actual Result?

Jest fails on import ... line (see screenshot below)
Current upstream issue, but solution did not work for us:
https://stackoverflow.com/questions/55794280/jest-fails-with-unexpected-token-on-import-statement
Reasoning: jest uses node, and node doesn't understand ES6 imports

Current Strategy

[ ] Fix it now
[x] Fix it later
[ ] Ignore it

Additional Details/Screenshots

[RGPosadas]

Tests disabled for now until we have more bandwidth to work on this

[RGPosadas]

Possible solution:
https://stackoverflow.com/questions/38740165/jest-ignore-lines-for-code-coverage

[RGPosadas]

Update to someone who wants to pick this up:
Through working on this bug, Detox should have been initialized along with Jest, therefore will work on #31 and see if this bug is recreated

[RGPosadas]

BLOCKS:
#31

[RGPosadas]

UPDATE:
Blocks future testing efforts
Possible babel issue/config

[RGPosadas]

UPDATE-2:
Reconfigured repo from scratch, but issue still happens specifically on react-native-screens after applying all recorded methods to solve uncompiled ES6 modules

Filed this in hopes of someone answering it:
https://stackoverflow.com/questions/60425485/jest-test-fails-on-react-native-screens-even-after-being-compiled-through-transf