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

Deprecate in favor of tasty? #62

Open
Bodigrim opened this issue Apr 24, 2022 · 6 comments
Open

Deprecate in favor of tasty? #62

Bodigrim opened this issue Apr 24, 2022 · 6 comments

Comments

@Bodigrim
Copy link

This package is on life support for at least five years and requires regular bumps from Hackage trustees to be compatible with the latest ecosystem. It's only a matter of time when revisions would no longer be enough. I'd like to mark it deprecated in favor of tasty (since migration from test-framework to tasty is mostly a matter of changing imports) to give a clear signal to clients that it's time to move on.

@sol
Copy link
Member

sol commented Apr 25, 2022

For what reason should we specifically recommend tasty over hspec or HTF from a repository that is hosted under the haskell organization?

@chessai
Copy link
Member

chessai commented Apr 25, 2022

Right. I don't think we should recommend a single thing, but just deprecate and say "use something else", possibly with a list of alternatives.

@sol
Copy link
Member

sol commented Apr 25, 2022

As long as that list is ordered by popularity I'm fine 🤣

@Bodigrim
Copy link
Author

@sol as I said, that's because "migration from test-framework to tasty is mostly a matter of changing imports". tasty was built as a successor to test-framework, and design decisions are very similar. With all due respect, migrating to hspec requires a complete rewrite, but I don't mind mentioning it as an option.

@sol
Copy link
Member

sol commented Apr 26, 2022

@Bodigrim not putting unnecessary burden on existing users of test-framework makes sense. Here is my perspective:

  • test-framework has been stable for years, I don't see a compelling technical reason for urging people that are happy with test-framework to move.
  • Looking at the commit history, maintenance overhead seem to be pretty low. I'm happy to take over maintenance if that helps. **
  • Competition is a good thing. Lack of competition leads to lower quality and hurts the end user (we have a lot of historic evidence for this).

** Conflict of interests: I'm also the maintainer of hspec, but I've been maintaining HUnit for the last 7 years without biasing it towards hspec in any way.

@andreasabel
Copy link
Member

There are tons of dependencies still on this package, see https://packdeps.haskellers.com/reverse/test-framework. So, no to deprecation. I see test-framework as simply a stable package that doesn't get any new features. Users that want new features can be directed to tasty, hspec or any other alternative...

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