[low priority] Rename repo to better reflect purpose

Question

[low priority] Rename repo to better reflect purpose

diwakergupta opened this issue 2 years ago · 7 comments

This repo now has tests for both 2.1 and 2.2. Opening this is as a low-priority issue for later: repo name should better reflect its purpose, given it'll likely be heavily used for the next hard-fork as well.

Answer 1 · 2023-05-03T13:31:56.000Z

I'm thinking we should rename this sooner rather than later. Another consideration if this repo would better belong in the stacks-network, and even somewhere under the stacks-blockchain repo.

Thoughts @obycode @friedger @kantai @lgalabru @saralab

Answer 2 · 2023-05-03T21:00:22.000Z

stacks-blockchain has integration tests in rust, therefore, I think, these devnet-js tests are better as a separate repo. Organisation does not matter too much to me.

It should also inspire developer to test their contracts with devnet-js

Name: stacks-blockchain-devnet-testing

Answer 3 · 2023-05-03T22:51:27.000Z

I agree that these tests should be considered useful examples for other developers to test their contracts with devnet-js, but I'd also like to see these tests end up in the stacks-blockchain repository -- we'd have to figure out how to structure their placement there (i.e., could be a top-level /testing/ directory), but I think it'd be great to integrate devnet-js testing into that repo's CI.

Answer 4 · 2023-05-05T06:46:48.000Z

As a non-rust developer, I am scared to explore stacks-blockchain repo. If it is clear from the top-level that js developers can benefit, then one mono-repo might work.

Answer 5 · 2023-05-18T15:55:36.000Z

Once done, this should be part of https://github.com/friedger/awesome-stacks-chain

Answer 6 · 2023-06-26T17:05:08.000Z

I renamed to stacks-e2e-testing.

Answer 7 · 2023-06-26T17:06:33.000Z

I don't know what procedure to follow to decide if it should move inside the stacks-blockchain repo. I think that can be opened as an issue on that repo if desired.