Skip to content

Conversation

@mansona
Copy link
Contributor

@mansona mansona commented Oct 5, 2025

This allows you to have a programatic build of your test assets and pass into the testem binary where the build location actually is.

Note: I only exposed config_dir because I needed the config to still stay in process.cwd(). I think it might make more sense to always search for config in process.cwd() but that's obviously a change that would need a major bump so I'm not necessarily proposing it right now.

@mansona
Copy link
Contributor Author

mansona commented Oct 6, 2025

Hey thanks @johanneswuerbach for running the CI job (at least I assume it was you 😂 )

It looks like the test failures aren't actually related to this change 🤔 is there something I can do to help unblock this or is it all just going to be stuff on your side?

@johanneswuerbach
Copy link
Member

@mansona yes it was me, I'll try to find some time to look into those CI failures today, the pipeline wasn't used for some time :-/

@johanneswuerbach
Copy link
Member

CI on main should be green again, would you mind rebasing your branch?

@mansona
Copy link
Contributor Author

mansona commented Oct 8, 2025

@johanneswuerbach done! I think I need another approval though for CI 🫠 😂

@johanneswuerbach johanneswuerbach merged commit d0b3459 into testem:master Oct 8, 2025
9 checks passed
@mansona
Copy link
Contributor Author

mansona commented Dec 10, 2025

@johanneswuerbach it looks like the latest release didn't make it to npm 🤔 is this an automated thing or do you do releases manually?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants