1.1 --- /dev/null Thu Jan 01 00:00:00 1970 +0000
1.2 +++ b/media/webrtc/trunk/testing/gtest/samples/sample2_unittest.cc Wed Dec 31 06:09:35 2014 +0100
1.3 @@ -0,0 +1,109 @@
1.4 +// Copyright 2005, Google Inc.
1.5 +// All rights reserved.
1.6 +//
1.7 +// Redistribution and use in source and binary forms, with or without
1.8 +// modification, are permitted provided that the following conditions are
1.9 +// met:
1.10 +//
1.11 +// * Redistributions of source code must retain the above copyright
1.12 +// notice, this list of conditions and the following disclaimer.
1.13 +// * Redistributions in binary form must reproduce the above
1.14 +// copyright notice, this list of conditions and the following disclaimer
1.15 +// in the documentation and/or other materials provided with the
1.16 +// distribution.
1.17 +// * Neither the name of Google Inc. nor the names of its
1.18 +// contributors may be used to endorse or promote products derived from
1.19 +// this software without specific prior written permission.
1.20 +//
1.21 +// THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
1.22 +// "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
1.23 +// LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
1.24 +// A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
1.25 +// OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
1.26 +// SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
1.27 +// LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
1.28 +// DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
1.29 +// THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
1.30 +// (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
1.31 +// OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
1.32 +
1.33 +// A sample program demonstrating using Google C++ testing framework.
1.34 +//
1.35 +// Author: wan@google.com (Zhanyong Wan)
1.36 +
1.37 +
1.38 +// This sample shows how to write a more complex unit test for a class
1.39 +// that has multiple member functions.
1.40 +//
1.41 +// Usually, it's a good idea to have one test for each method in your
1.42 +// class. You don't have to do that exactly, but it helps to keep
1.43 +// your tests organized. You may also throw in additional tests as
1.44 +// needed.
1.45 +
1.46 +#include "sample2.h"
1.47 +#include "gtest/gtest.h"
1.48 +
1.49 +// In this example, we test the MyString class (a simple string).
1.50 +
1.51 +// Tests the default c'tor.
1.52 +TEST(MyString, DefaultConstructor) {
1.53 + const MyString s;
1.54 +
1.55 + // Asserts that s.c_string() returns NULL.
1.56 + //
1.57 + // <TechnicalDetails>
1.58 + //
1.59 + // If we write NULL instead of
1.60 + //
1.61 + // static_cast<const char *>(NULL)
1.62 + //
1.63 + // in this assertion, it will generate a warning on gcc 3.4. The
1.64 + // reason is that EXPECT_EQ needs to know the types of its
1.65 + // arguments in order to print them when it fails. Since NULL is
1.66 + // #defined as 0, the compiler will use the formatter function for
1.67 + // int to print it. However, gcc thinks that NULL should be used as
1.68 + // a pointer, not an int, and therefore complains.
1.69 + //
1.70 + // The root of the problem is C++'s lack of distinction between the
1.71 + // integer number 0 and the null pointer constant. Unfortunately,
1.72 + // we have to live with this fact.
1.73 + //
1.74 + // </TechnicalDetails>
1.75 + EXPECT_STREQ(NULL, s.c_string());
1.76 +
1.77 + EXPECT_EQ(0u, s.Length());
1.78 +}
1.79 +
1.80 +const char kHelloString[] = "Hello, world!";
1.81 +
1.82 +// Tests the c'tor that accepts a C string.
1.83 +TEST(MyString, ConstructorFromCString) {
1.84 + const MyString s(kHelloString);
1.85 + EXPECT_EQ(0, strcmp(s.c_string(), kHelloString));
1.86 + EXPECT_EQ(sizeof(kHelloString)/sizeof(kHelloString[0]) - 1,
1.87 + s.Length());
1.88 +}
1.89 +
1.90 +// Tests the copy c'tor.
1.91 +TEST(MyString, CopyConstructor) {
1.92 + const MyString s1(kHelloString);
1.93 + const MyString s2 = s1;
1.94 + EXPECT_EQ(0, strcmp(s2.c_string(), kHelloString));
1.95 +}
1.96 +
1.97 +// Tests the Set method.
1.98 +TEST(MyString, Set) {
1.99 + MyString s;
1.100 +
1.101 + s.Set(kHelloString);
1.102 + EXPECT_EQ(0, strcmp(s.c_string(), kHelloString));
1.103 +
1.104 + // Set should work when the input pointer is the same as the one
1.105 + // already in the MyString object.
1.106 + s.Set(s.c_string());
1.107 + EXPECT_EQ(0, strcmp(s.c_string(), kHelloString));
1.108 +
1.109 + // Can we set the MyString to NULL?
1.110 + s.Set(NULL);
1.111 + EXPECT_STREQ(NULL, s.c_string());
1.112 +}
