Skip to content

Conversation

@bznein
Copy link
Collaborator

@bznein bznein commented Nov 4, 2025

Also solves a few flakiness issues and reverts an accidental change.

Before asking for reviews, here is a check list of the most common things you might need to consider:

  • updating the Changelog
  • writing unit tests
  • checking if your changes affect other coins or tokens in unintended ways
  • testing on multiple environments (Qt, Android, ...)
  • having an AI review your changes

@bznein bznein requested a review from thisconnect November 4, 2025 09:57
Copy link
Collaborator

@thisconnect thisconnect left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, with one point about not using id for tests, please change to data-testid


// First, clean up cache and headers.
try {
const basePath = path.resolve(__dirname, '../../../../appfolder.dev/cache');
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would it help to use nodejs built in process.cwd() function here instead of traversing up the directory structure?

https://nodejs.org/docs/latest/api/process.html#processcwd

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

IIRC I tried but since we launch the tests from frontends/web, process.cwd() resolves to that dir. However I just slightly refactored it to be much cleaner in github CI (and moderately cleaner in non-CI :D )

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ah I see, no strong opinion. It was more a question.

I guess the Makefile task starts from the root, but then cd into frontends/web

cd ${WEBROOT} && $(MAKE) test-e2e


const { stdout } = await execAsync(cmd);
return stdout.trim();
}
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't understand engouh docker and am always confused about when to use spawn, fork or exec.

It looks very cool what you do in this file with the regtest, but I am not the right person to review this.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, I will revisit this file, add some comments, and ask for another reviewer :)

@bznein bznein force-pushed the regtest branch 8 times, most recently from fa11eee to 62f6f60 Compare November 5, 2025 12:04
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.

2 participants