Skip to content
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

Discuss modules in CITGM #35

Open
wesleytodd opened this issue Mar 19, 2020 · 6 comments
Open

Discuss modules in CITGM #35

wesleytodd opened this issue Mar 19, 2020 · 6 comments

Comments

@wesleytodd
Copy link
Member

On the Express TC meeting we discussed testing for our dependencies, especially for v5 and were thinking we need a better way to integrate groups of modules to CITGM. What do other frameworks do for this?

@gireeshpunathil
Copy link
Member

gireeshpunathil commented Mar 19, 2020

better way to integrate groups of modules to CITGM

Just thinking loud in terms of what those could be:

  • ability to introduce a module into the suite
  • ability to define change control (which version to test, when to upgrade)
  • ability to send a beta for testing

?

@Ethan-Arrowood
Copy link
Contributor

I believe someone released a package for testing dependencies of any npm project recently. I'll have to find that or maybe someone else remembers what it was called

@ljharb ljharb changed the title Disucss modules in CITGM Discuss modules in CITGM Mar 19, 2020
@gireeshpunathil
Copy link
Member

one of the idea / question that came up for discussion is: how frameworks can better leverage CITGM. For example, if a class of test can be (dynamically?) organized in such a manner that a set of modules that depend on the framework is selected and tested, and accounted together? that way, we will be testing those modules for node.js stability, as well as the stability of the framework, in one shot, against a target node.js version.

This would be of great value for frameworks before they release their majors?

We could clone and maintain a copy of the test suite that fits the frameworks' purpose, or decide to reuse the existing CITGM, if it already is capable of catering to this use case.

@BethGriggs
Copy link
Member

We've had similar discussions in the package maintenance WG:

@andrewhughes101 is currently looking at what we thought step one would be - which was how can framework authors get the list of modules that depend on them, and filter them down in a useful way.

@wesleytodd
Copy link
Member Author

wesleytodd commented May 28, 2020

We chatted about this a bit on todays meeting, and wanted to get feedback from folks on the @nodejs/web-server-frameworks team on the work being done on this tool:

pkgjs/wiby#1

It is very early, but feedback on if the direction seems useful, would be helpful to keep it going in the right direction.

EDIT: forgot the context!

This tool will help module authors test their downstream packages. So you can test your upcoming releases with packages which depend on you.

@wesleytodd
Copy link
Member Author

I know this one is old, but I am thinking that we should put together a list of action items which need to be addressed to get express back into CITGM. Not sure if we should use this issue or make a new one. Going to add the agenda tag so we can discuss.

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

No branches or pull requests

4 participants