I see

vitest

is the test runner bundled in the starter templates. Is that what most of you are using? It’s the first I’ve heard of this framework, having mainly used Jest. Looking at the docs it looks the same API as Jest. Any gotchas to be aware of if switching to this from Jest?

Nope they made it work pretty well out of the box for people used to jest. It's way faster too!

Excellent! Just setting up an E2E test with it for my REST API…

Yeah that's the approach right now but we have a new sst.Parameter thing coming up which will work without that

is it possible for the deployments from

sst start

triggered by hitting Enter to write their outputs to a file that I can read from my tests? Or does it have to explicitly go through the

sst deploy

command?

It should be doing that, is it not?

will restart and check…

I've actually never used this feature haha

haha. Serverless Framework had an export-env plugin that I always use for this.

our new idea is to introduce sst.Parameter which saves values in SSM. You can attach them to functions and it'll autoload them on start. And then for tests we just load all of the ones in your whole app before running

that’s nice if it will autoload them for you as I’ve always ended up building

ssm-helper

util type modules for this

so is this available now?

It's technically published but we haven't released it yet, there's some design choices we need to make but I'm hoping this comes out in a month or so

so this Parameter module isn’t yet part of the framework libraries, I would need to include it in my own code if I want to get the codegen today, is that right?

Yeah and the other awkward thing is Parameter.use(func, ...)

ok. I might just leave it for now and just parse the outputs.json file

yeah we're in a weird middle phase because I'm working on rethinking our approach with testing using Parameter but I also ran into the same need, was just manually passing it as an env param when I ran the test command. But now that I think of it you could probably do

import { State } from "@serverless-stack/core"

State.getStage(process.cwd())

got it working. Just reading stack config like so:

const readStackConfig = () => {
  const stackOutputs = JSON.parse(
    readFileSync(join(__dirname, '../../../../stacks/stack-outputs.json')).toString()
  )
  const stackName = `${State.getStage(process.cwd())}-sst-twitter-exporter-MyStack`
  return stackOutputs[stackName]
}

nice! yeah and jest was also a nightmare to configure with esm

Damn Vitest is really great, setting it up took a second and it’s so fast! Somethings that annoyed me about Jest are fixed or configurable in Vitest. Happy that I saw this thread 🙌