-
Notifications
You must be signed in to change notification settings - Fork 48
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
Port F18 unittests to gtest #995
Comments
Hi @RichBarton-Arm is someone working on this currently? |
This ticket seems like we need a port of all unittests/ files into a gtest based framework, but given that there is no unittest framework using gtest, should we have that first? |
Hi @Sameeranjoshi |
@Sameeranjoshi has committed https://reviews.llvm.org/D80377 which puts the infrastructure in place. All new tests can be added as gtest tests. We now need to port the existing tests over to this format. |
A fresh patch in this direction: https://reviews.llvm.org/D97403 Thank you @ashermancinelli! |
Better document each test in output formatting tests. Use GTest primitives and infrastructure in same spirit as [[ https://reviews.llvm.org/D97403 | D97403 ]]. [[ flang-compiler/f18#995 (comment) | See legacy github issue linked here ]] for additional context. Reorganize long test cases to be more readable. Reviewed By: awarzynski, klausler Differential Revision: https://reviews.llvm.org/D98303
Better document each test in output formatting tests. Use GTest primitives and infrastructure in same spirit as [[ https://reviews.llvm.org/D97403 | D97403 ]]. [[ flang-compiler/f18#995 (comment) | See legacy github issue linked here ]] for additional context. Reorganize long test cases to be more readable. Reviewed By: awarzynski, klausler Differential Revision: https://reviews.llvm.org/D98303
Better document each test in output formatting tests. Use GTest primitives and infrastructure in same spirit as [[ https://reviews.llvm.org/D97403 | D97403 ]]. [[ flang-compiler/f18#995 (comment) | See legacy github issue linked here ]] for additional context. Reorganize long test cases to be more readable. Reviewed By: awarzynski, klausler Differential Revision: https://reviews.llvm.org/D98303
https://reviews.llvm.org/D105315 concludes the porting of We still need to port |
Better document each test in output formatting tests. Use GTest primitives and infrastructure in same spirit as [[ https://reviews.llvm.org/D97403 | D97403 ]]. [[ flang-compiler/f18#995 (comment) | See legacy github issue linked here ]] for additional context. Reorganize long test cases to be more readable. Reviewed By: awarzynski, klausler Differential Revision: https://reviews.llvm.org/D98303
After #941 is complete, F18 will have a directory unittests that contain tests written in C++ that wrap various internals of F18's runtime or shared utilities in a test harness and test them. This is supported by some custom test harness code.
LLVM projects use the gtest framework for tests of this type. See https://github.com/llvm/llvm-project/tree/master/clang/unittests for an example of this.
The F18 tests need to be ported to also use this framework.
The text was updated successfully, but these errors were encountered: