[chore]: info about tests to readme

[MCJOHN974]

Description

Closes: no issue

I often use this command and sometimes loose it. Extract it from readme will be easier then extracting from my shell history. Is this readme okish place for this command or maybe signer/README.md will fit better?

Changes

Added few lines to readme

Testing Information

Checklist:

• I have performed a self-review of my code
• My changes generate no new warnings
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules

[matteojug]

Isn't this already covered by:
https://github.com/stacks-network/sbtc/blob/394dc72e5bc31db2e51d88f3f7445a724072fa56/README.md?plain=1#L82-L84
?

[MCJOHN974]

Isn't this already covered by:

https://github.com/stacks-network/sbtc/blob/394dc72e5bc31db2e51d88f3f7445a724072fa56/README.md?plain=1#L82-L84

?

@matteojug I trying to use our make commands and they sometimes do not work well. This manual docker compose works fine every time I use it

Maybe it is a call to add some changes to Makefile, but I personally ok to just call this docker compose manually =)

[djordon]

@matteojug I trying to use our make commands and they sometimes do not work well. This manual docker compose works fine every time I use it

Maybe it is a call to add some changes to Makefile, but I personally ok to just call this docker compose manually =)

@MCJOHN974 what specific issues have you run into and how often are you running into them? What you added to the README is the make integration-env-up command but without basically running pnpm --filter run synth.

[MCJOHN974]

I can't reproduce any particular issue, however it still can be useful for running integration tests and look at emily logs

[MCJOHN974]

I don't mind to close it though

[djordon]

Closing, since we cannot reproduce the underlying issue. And if we could, we should probably address that directly by updating the make command or solving the underlying problem.