-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: add e2e test framework #31
Conversation
looks good to me. |
Signed-off-by: Anmol Sharma <anmolsharma0234@gmail.com>
6785ea6
to
7855a1d
Compare
Signed-off-by: Anmol Sharma <anmolsharma0234@gmail.com>
run: docker compose -f "./e2e/helpers/docker/docker-compose.yml" up -d | ||
- name: Cache node modules | ||
id: cache-node-modules | ||
uses: actions/cache@v4 | ||
with: | ||
path: node_modules | ||
key: node-modules-${{ hashFiles('package-lock.json') }} | ||
- name: Install Dependencies | ||
if: steps.cache-node-modules.outputs.cache-hit != 'true' | ||
run: npm install | ||
- name: Start indexer | ||
run: npm run start:e2e > indexer.log 2>&1 & | ||
- name: Wait for indexer to become available |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems Good to me . What is your opinion regarding putting indexer also in a container ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do you mean, creating a Dokcerfile, building the image, and running that image here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, we can create a docker image of the indexer and run it in the same service as bitcoind
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The problem here is that we'd need to build the image again and again for every run. This could slow down the CI considerably.
This will definitely be a good change but let's do it in a future PR.
No description provided.