Great work! I think you covered things nicely and I like that the framework is auto-detected. I think it's fine to declare jest/jasmine as any since it's internal and we don't know the user's version.

I think that since the user should be interacting with jest/jasmine directly in their tests so we should consider keeping the testingFrameworks object private to shallow-render. I couldn't imagine an end-user writing a test with Shallow.testingFramework.spyOn and wouldn't want to encourage it.

What do you think about converting the public static property to a singleton module that can be used internally like:

import { testFramework } from './lib/test-framework';
testFramework.spyOn();

This could be accomplished by converting the getAvailableTestFramework function in lib/test-framework to export the singleton like this:

// I've taken some liberties in reducing the detection logic you used in `getAvailableTestFramework`
export const testFramework = typeof jest === 'undefined'
  ? new JasmineFramework()
  : new JestFramework();

I think we could probably put out a pre-release NPM package that we can use to test out in a sample project with Jest.

Thanks again for the PR, glad to have your support!

Thanks for reviewing my PR, I've extracted the public class property to a singleton module as you suggested.

I'd be happy to keep contributing to this project 🎉

Cool, gonna test our your changes. I noticed some weirdness in the TSC output with an import, I think I have a fix and I'll submit a PR to your branch when I'm done.

Once this is all merged, I'll add you to the contributors list!

Looks like you already resolved the import issue in your latest change. This tests well, I created an angular 6 project and tests ran with Karma and Jest!

Awesome guys. I'll test this when I get some time as well.