Skip to content

Strategy for porting tests? #422

Description

@starpit

Hey there, nice project! I tried having Opus 5 apply cpp2rust to my large c++ code base. When I asked it to port the tests, it (also) ported gtest itself! Surely there is a more sane approach to this, and was curious if you had some thoughts.

For example, Claude suggests this, but surely this is also not a complete approach:

make gtest opaque, lower TEST_F/EXPECT_EQ onto #[test]/assert_eq!

btw, i have a mountain of cpp2rust features Claude added to support my (pretty complex) code base, if you are interested. I was holding them until I got it actually fully working. Which, to be honest, I'm not yet confident is possible. But am willing to try.

No activity

Activity on this issue will appear here.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions