Hi @stephencelis,

Thanks for creating this snapshot testing framework!
I was comparing this framework with the other snapshot framework (https://github.com/uber/ios-snapshot-test-case)(FBSnapshotTestCase) to know which features are supported.

What I like about this framework is the API, in which you can easily specify the device (iPhoneSE or iPad), while for with the FBSnapshotTestCase you

rendering a component with <> ... </> seems troublesome and often return null instead of children

functional-component.js

import React from 'react';
export default ({ message }) => <span>{message}</span>;

component.js

import React from 'react';

import FunctionalComponent from './functional-component';

export default ({ message, show }) => {
  return (
    <>
  

Currently, when I follow the XCTest naming guidelines and write test names like this:

    func testBasicRendering() {
        expect(snapshotView).toMatchSnapshot()
    }

I get files named like this:

reference_testbasicrendering@3x.png

I would have expected the name to be reference_basicrendering, so the test prefix should be removed as it is part of any

Hi there

Awesome library guys. So helpful. Like it a lot!

I'd like to propose a feature request: Disable auto-creating new snapshots and instead print out the content as preview.

Using the "--update-snapshots" one can still update/create those missing snapshots.

Thx for your consideration
Best
Dimitri

Having spent several hours yesterday pairing with a new user, we copied a lot of examples from our docs, and in every case, we had to paste in our namespace ApprovalTests:: - it got very old, very quickly - and I ended up agreeing with this:

https://twitter.com/lefticus/status/1207890691948339200

Please, I implore you, in the name of all that is good, do NOT use using namespace in

I have to always look up the syntax for updating snapshot values https://github.com/bahmutov/snap-shot-it#advanced-use

I should add a few aliases to SNAPSHOT_UPDATE=1 npm test like UPDATE_SNAPSHOTS=1 ...

If I file doesn't end with a new line many other reporters goof up. Text files should probably always check that the last character is a \n and add one if needed

The built in error message is very opaque (necessary because it has to be generic) but users can likely provide a more helpful friendly message customised to their tests (or e.g. when the diff just isn't useful). Therefore an option to customise this message would be useful.

This would only really be usable once #28 is implemented.

I would love to see this repo cover a scenario where you navigate across pages. Ideally covering navigation handled two ways: one via a simple stencil route link, and another via a button which calls a function to programatically navigate.

For example:

1. Load the root url: "/"
2. Find a navigation link: <stencil-route-link url='/page-2' ...
3. Click the link
4. Assert page is Page 2

Current tests are starting to be hard to reason about. Some clarification about the behaviour each test is attempting to verify is getting more essential.

Describe the solution you'd like

Make each test case group a single file testing all the behaviours with module and test doc string explaining the purpose

Describe alternatives you've considered
N/A

Additional context
T