Transfer to Fortran-lang organization?
awvwgk opened this issue · 7 comments
This project was originally developed as light-weight testing framework for TOML Fortran and the Fortran package manager, where it has been redistributed within the testsuite. There are now a couple of redistributed variants around, mostly MIT or Apache-2.0 licensed:
- https://github.com/fortran-lang/fpm/blob/master/test/fpm_test/testsuite.f90
- https://github.com/toml-f/toml-f/blob/main/test/tftest/testsuite.f90
- https://github.com/LKedward/fhash/blob/master/test/TestLite.f90
- https://github.com/grimme-lab/mctc-lib/blob/main/src/mctc/env/testing.f90
We discussed about this and other testing frameworks at @fortran-lang in several issues and I offered to transfer it to @fortran-lang:
cc @certik @zoziha @everythingfunctional @milancurcic @LKedward @hsnyder @jvdp1
I hope that fortran-lang
can maintain a testing-framework, and it will go further with the help of fortran-lang
organization. It will be standardized, accepted and improved by the community, which is a very far-reaching good thing!
Thank you @awvwgk for your generous donation (test-drive
) to fortran-lang!🎉
I am 150% in favor of fortran-lang/test-drive. It's relatively small and simple, and has the coolest sounding name I've heard of a Fortran project in a long time.
That sounds like a great idea to me, especially if it is used by fpm and stdlib. Thank you @awvwgk
I think this looks good as a testing framework. Why not simplify:
call check(error, all(input == expected))
if (allocated(error)) return
to:
if (check(error, all(input == expected))) return
Beyond that, the only other way to simplify is using macros, but I like that this is very usable without macros.
It seems the test-drive
's internal code is relatively straightforward and I think we should be able to maintain this as a community.
So +1 to move under fortran-lang.
Alright, I'll went ahead and transferred the repository to @fortran-lang.
Why not simplify:
call check(error, all(input == expected)) if (allocated(error)) returnto:
if (check(error, all(input == expected))) returnBeyond that, the only other way to simplify is using macros, but I like that this is very usable without macros.
@certik Let's continue this discussion in a separate issue.