googletest and googlemock moved to GitHub

[Billy Donahue]

The GoogleTest and GoogleMock projects have been moved to GitHub.

http://github.com/google/googletest

http://github.com/google/googlemock

The GitHub migration tool is pretty good! The bug database has been migrated. The code change history has been preserved. The Wiki has been converted to markdown format and moved to the docs/ directory of each of the two projects.

Several of the links in those docs will need to be updated, and I've started on doing that.

Discussion groups (these mailing lists) are on google Groups and are unaffected.

The old code.google.com pages are going to go read-only in a few days.

Exciting times.

[Alex Shaver]

I just pulled google mock, and there wasn't a gtest directory within it. Similarly, if you just look at the source on github it isn't included there. But the documentation (and cmake, autoreconf, etc.) expect it to be there.

[Billy Donahue]

It's an oversight. Thanks.

Alex, we're going to try something new, and put the googlemock and googletest projects into one repository.

The cmake and autoreconf scripts will have to be updated.

We're rushing to figure these problems out right now, but I think it will settle out and we'll be better off in the end. Sorry for the churn.

Keep these reports coming in, please.

--

---
You received this message because you are subscribed to the Google Groups "Google C++ Testing Framework" group.
To unsubscribe from this group and stop receiving emails from it, send an email to googletestframe...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Billy Donahue]

Hi all,

To simplify things, we're going to be merging googlemock and googletest into a single GitHub repository from now on.

https://github.com/google/googletest

I'm still working out the documentation etc, but the code is where it will be for a while.

Users can follow this one repository to stay up to date with both products, which we think should be easier on them and certainly on us.

Thanks!

[Billy Donahue]

I should delete that section. Thanks.  The patches should go through the usual GitHub Pull Request process. Thanks.

On Wed, Oct 7, 2015 at 9:38 PM, Arieh Schneier <arieh.s...@gmail.com> wrote:

Now that the project has moved to github what is the process for submitting patches?

The devguide is out of date as it discusses svn: https://github.com/google/googletest/blob/master/googletest/docs/DevGuide.md

[Alex Shaver]

Another question, (this seemed like the reasonable thread to ask in, rather than a new one): Is there any thought to actually merging the suite into one library? It's weird to have to pull in googlemock "gmock/gmock-matchers" in a test that isn't using mocks anyway. Given that they're already weirdly coupled, why not just merge together?

To unsubscribe from this group and stop receiving emails from it, send an email to googletestframework+unsub...@googlegroups.com.

[Billy Donahue]

Yes. That's the goal.

To unsubscribe from this group and stop receiving emails from it, send an email to googletestframe...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--

---
You received this message because you are subscribed to the Google Groups "Google C++ Mocking Framework" group.
To unsubscribe from this group and stop receiving emails from it, send an email to googlemock+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/googlemock/6875b0c4-e696-4068-a430-798fa163d5cd%40googlegroups.com.

[Alex Shaver]

Awesome, thanks.

[Anurag Jain]

We are extensively using gmock to unit test our code, the gmock version that we are using is 1.5.0

We are uplifting our code to be 64 bit compliant. This means we have to uplift our unit test written in Gmock too.

 

Do we need to upgrade the gmock version to be able to compile in 64 bit or Gmock 1.5.0  will suffice the need?

[Billy Donahue]

Wow that's very old.

You're better off with a supported version.

--

---
You received this message because you are subscribed to the Google Groups "Google C++ Mocking Framework" group.
To unsubscribe from this group and stop receiving emails from it, send an email to googlemock+...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/googlemock/1ffb0de5-869c-4901-bcdd-53cdfebf2a78%40googlegroups.com.

[David Wallace]

The gtest/gmock documentation links have just started redirecting to a GitHub pull request recently.  (I just restarted Firefox and watched all my open doc pages change to the same pull request).  This is really not acceptable for developers who don't want anything to do with GitHub or the latest sources, but just want to be able to read the docs on how to do something in gtest/gmock version 1.6 (which is what we're using).  Is there a reason you can't just leave up the old web pages for people to look at?  I've got links to the doc pages in our internal Wiki documentation on how to do unit testing at our company, all of which now seem to be obsolete.  And the internal links on the GitHub .md doc pages now give a bunch of 404s (e.g., the links from https://github.com/google/googletest/blob/master/googlemock/docs/v1_6/Documentation.md).  The new pages also lack the internal table of contents that used to be the fastest way to find something.  If it ain't broke...

Dave W.

[Billy Donahue]

We can't spend much time on fixing v1.6 documentation.

If you have a PR to patch it up, that's great.

Code.google.com announced it was closing shop and we had to scramble. The best import tool available at the time did what it did, and it seems the import was imperfect. Sorry about that.

--

---
You received this message because you are subscribed to the Google Groups "Google C++ Testing Framework" group.
To unsubscribe from this group and stop receiving emails from it, send an email to googletestframe...@googlegroups.com.

[Anurag Jain]

Billy,

I tried compiling the gmock 1.5.0 in 64 bit, it compiles smooth, even
the gmock unit tests that we have written in 64 bit are running.
we found that there are considerable amount of change from gmock 1.5.0
to googlemock 1.7.0, causing us to change lot of code.

if we can still remain in gmock 1.5.0 64 bit, would that be ok as it
can save a lot of effort for us ?

-Anurag.

[Billy Donahue]

You can of course keep using whatever you want to use.

But it's unsupported. You should probably invest in upgrading.

[Zhanyong Wan (λx.x x)]

On Wed, Jan 13, 2016 at 7:33 AM, Anurag Jain <anurag...@gmail.com> wrote:

Billy,

I tried compiling the gmock 1.5.0 in 64 bit, it compiles smooth, even
the gmock unit tests that we have written in 64 bit are running.
we found that there are considerable amount of change from gmock 1.5.0
to googlemock 1.7.0, causing us to change lot of code.

This is a bit surprising.  Most of changes we made to gmock are backward compatible and shouldn't cause a lot of churn in user code.  What kind of changes did you have to make?

 

To view this discussion on the web visit https://groups.google.com/d/msgid/googlemock/CAJrSN06WL3TSses9yJ%2BNQWL0cyuQYGaAeT%3DaOy-DuBqtviC88A%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

--

Zhanyong

[Anurag Jain]

we are using GMOCK_ARG_ to write few macros, which has parameters
changed in 1.7.0, so we have to correct all our macros to take 2nd
argument as number of args, if there is an alternative , please let me
know.

1.7.0 - GMOCK_ARG_(tn, 1, __VA_ARGS__)
1.5.0 - GMOCK_ARG_(tn, F, 1)

-Anurag

[Zhanyong Wan (λx.x x)]

GMOCK_ARG_ is an internal macro and not supposed to be used directly by a user (in general, all gtest/gmock macros that end with _ are internal and shouldn't be used).  It's documented as such: https://github.com/google/googletest/blob/master/googlemock/include/gmock/gmock-generated-function-mockers.h#L342

If you use an internal macro, your code may break when upgrading to a new version of gtest/gmock.  Worse, the breakage may be silent (your tests may be passing even when they should fail).  Therefore please don't do that.

What are you really trying to achieve with GMOCK_ARG_?

To view this discussion on the web visit https://groups.google.com/d/msgid/googlemock/CAJrSN06wnktAyyn-ttcaXbqyPMGTAkgydrfJg1dpq0LBkPK1bw%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

--

Zhanyong