chore(trustchain): simplify test folders

[gre]

✅ Checklist

• npx changeset was attached.
• Covered by automatic tests.
• Impact of the changes:
  • tests only

📝 Description

the lib/ output of the library no longer is polluted by test scenarios

test scenarios and test helpers are in /tests and scenario records are in /mocks outside of the src folder

(NB: it can't be a __tests__ because Jest default's config would still consider these as runnable tests)

a sdkForName helper is given to scenario to simplify the boilerplate you need to do to create a sdk

no longer need to generate individual jest test for each scenario

We simplify the necessary boilerplate to run the tests by having one test file that run them all:

fs.readdirSync(mockFolder).forEach(file => {
  if (!file.endsWith(".json")) return;
  const slug = file.slice(0, -5);
  const json = require(path.join(mockFolder, file));
  const mod = require(path.join(scenarioFolder, slug + ".ts"));
  test(slug, async () => {
    const scenario = mod.scenario;
    await replayTrustchainSdkTests(json, scenario);
  });
});

❓ Context

• JIRA or GitHub link:

---

🧐 Checklist for the PR Reviewers

• The code aligns with the requirements described in the linked JIRA or GitHub issue.
• The PR description clearly documents the changes made and explains any technical trade-offs or design decisions.
• There are no undocumented trade-offs, technical debt, or maintainability issues.
• The PR has been tested thoroughly, and any potential edge cases have been considered and handled.
• Any new dependencies have been justified and documented.
• Performance considerations have been taken into account. (changes have been profiled or benchmarked if necessary)

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
web-tools	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jul 11, 2024 11:59am

4 Skipped Deployments

Name	Status	Preview	Comments	Updated (UTC)
ledger-live-docs	⬜️ Ignored (Inspect)	Visit Preview		Jul 11, 2024 11:59am
ledger-live-github-bot	⬜️ Ignored (Inspect)	Visit Preview		Jul 11, 2024 11:59am
native-ui-storybook	⬜️ Ignored (Inspect)	Visit Preview		Jul 11, 2024 11:59am
react-ui-storybook	⬜️ Ignored (Inspect)	Visit Preview		Jul 11, 2024 11:59am

[KVNLS]

Can you keep the convention we have in most projects for tests and mocks folders, please? By using __tests__ and __mocks__

[gre]

ok but the problem is it doesn't work for the default jest config that wants to runs the files inside these even if they are outside of src. shouldn't we stay relatively jest standard?
(on top of these, they are not even jest tests)

[KVNLS]

Maybe we can add aliases for mocks and tests folder, wdyt?

[gre]

not possible with node.js path resolvers. here we will fs.read the files, it's not a require

[gre]

conflict solved. pr review answered. 👍

[mcayuelas-ledger]

IMHO test files should be named as follows :

(whatYouAreTesting|scenario).test.ts(x)

[gre]

@mcayuelas-ledger which test files?
i'm ok with the idea for all files that need to be run by Jest, which is not the case of scenario files (they are not test files but a script that can indeed by imported by tests, but also can be used standalone with the e2e script)

NB: if we start renaming the scenario files to .test.ts, Jest will start to run them and basically fails, since they are not test files, and then we need specific config to ignore them, which imo is bad (we want to embrace standard config as much as possible)

for the actual Jest files, this convention is now respected :)