2022-09-06 19:14:07 -04:00
|
|
|
|
// Copyright 2014 The Crashpad Authors
|
2014-08-15 22:33:14 -07:00
|
|
|
|
//
|
|
|
|
|
// Licensed under the Apache License, Version 2.0 (the "License");
|
|
|
|
|
// you may not use this file except in compliance with the License.
|
|
|
|
|
// You may obtain a copy of the License at
|
|
|
|
|
//
|
|
|
|
|
// http://www.apache.org/licenses/LICENSE-2.0
|
|
|
|
|
//
|
|
|
|
|
// Unless required by applicable law or agreed to in writing, software
|
|
|
|
|
// distributed under the License is distributed on an "AS IS" BASIS,
|
|
|
|
|
// WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
|
|
|
// See the License for the specific language governing permissions and
|
|
|
|
|
// limitations under the License.
|
|
|
|
|
|
|
|
|
|
#include "util/mac/mac_util.h"
|
|
|
|
|
|
|
|
|
|
#import <Foundation/Foundation.h>
|
|
|
|
|
#include <stdlib.h>
|
|
|
|
|
|
|
|
|
|
#include <string>
|
|
|
|
|
|
|
|
|
|
#include "base/mac/scoped_nsobject.h"
|
|
|
|
|
#include "base/strings/stringprintf.h"
|
|
|
|
|
#include "gtest/gtest.h"
|
|
|
|
|
|
2014-10-07 17:28:50 -04:00
|
|
|
|
namespace crashpad {
|
|
|
|
|
namespace test {
|
2014-08-15 22:33:14 -07:00
|
|
|
|
namespace {
|
|
|
|
|
|
|
|
|
|
// Runs /usr/bin/sw_vers with a single argument, |argument|, and places the
|
|
|
|
|
// command’s standard output into |output| after stripping the trailing newline.
|
2020-05-06 20:39:19 -04:00
|
|
|
|
// Fatal Google Test assertions report tool failures, which the caller should
|
|
|
|
|
// check for with ASSERT_NO_FATAL_FAILURE() or testing::Test::HasFatalFailure().
|
2014-08-15 22:33:14 -07:00
|
|
|
|
void SwVers(NSString* argument, std::string* output) {
|
|
|
|
|
@autoreleasepool {
|
|
|
|
|
base::scoped_nsobject<NSPipe> pipe([[NSPipe alloc] init]);
|
|
|
|
|
base::scoped_nsobject<NSTask> task([[NSTask alloc] init]);
|
|
|
|
|
[task setStandardOutput:pipe];
|
|
|
|
|
[task setLaunchPath:@"/usr/bin/sw_vers"];
|
|
|
|
|
[task setArguments:@[ argument ]];
|
|
|
|
|
|
|
|
|
|
@try {
|
|
|
|
|
[task launch];
|
|
|
|
|
}
|
|
|
|
|
@catch (NSException* exception) {
|
|
|
|
|
FAIL() << [[exception name] UTF8String] << ": "
|
|
|
|
|
<< [[exception reason] UTF8String];
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
NSData* data = [[pipe fileHandleForReading] readDataToEndOfFile];
|
|
|
|
|
[task waitUntilExit];
|
|
|
|
|
|
test: Use (actual, [un]expected) in gtest {ASSERT,EXPECT}_{EQ,NE}
gtest used to require (expected, actual) ordering for arguments to
EXPECT_EQ and ASSERT_EQ, and in failed test assertions would identify
each side as “expected” or “actual.” Tests in Crashpad adhered to this
traditional ordering. After a gtest change in February 2016, it is now
agnostic with respect to the order of these arguments.
This change mechanically updates all uses of these macros to (actual,
expected) by reversing them. This provides consistency with our use of
the logging CHECK_EQ and DCHECK_EQ macros, and makes for better
readability by ordinary native speakers. The rough (but working!)
conversion tool is
https://chromium-review.googlesource.com/c/466727/1/rewrite_expectassert_eq.py,
and “git cl format” cleaned up its output.
EXPECT_NE and ASSERT_NE never had a preferred ordering. gtest never made
a judgment that one side or the other needed to provide an “unexpected”
value. Consequently, some code used (unexpected, actual) while other
code used (actual, unexpected). For consistency with the new EXPECT_EQ
and ASSERT_EQ usage, as well as consistency with CHECK_NE and DCHECK_NE,
this change also updates these use sites to (actual, unexpected) where
one side can be called “unexpected” as, for example, std::string::npos
can be. Unfortunately, this portion was a manual conversion.
References:
https://github.com/google/googletest/blob/master/googletest/docs/Primer.md#binary-comparison
https://github.com/google/googletest/commit/77d6b173380332b1c1bc540532641f410ec82d65
https://github.com/google/googletest/pull/713
Change-Id: I978fef7c94183b8b1ef63f12f5ab4d6693626be3
Reviewed-on: https://chromium-review.googlesource.com/466727
Reviewed-by: Scott Graham <scottmg@chromium.org>
2017-04-04 00:35:21 -04:00
|
|
|
|
ASSERT_EQ([task terminationReason], NSTaskTerminationReasonExit);
|
|
|
|
|
ASSERT_EQ([task terminationStatus], EXIT_SUCCESS);
|
2014-08-15 22:33:14 -07:00
|
|
|
|
|
|
|
|
|
output->assign(reinterpret_cast<const char*>([data bytes]), [data length]);
|
|
|
|
|
|
test: Use (actual, [un]expected) in gtest {ASSERT,EXPECT}_{EQ,NE}
gtest used to require (expected, actual) ordering for arguments to
EXPECT_EQ and ASSERT_EQ, and in failed test assertions would identify
each side as “expected” or “actual.” Tests in Crashpad adhered to this
traditional ordering. After a gtest change in February 2016, it is now
agnostic with respect to the order of these arguments.
This change mechanically updates all uses of these macros to (actual,
expected) by reversing them. This provides consistency with our use of
the logging CHECK_EQ and DCHECK_EQ macros, and makes for better
readability by ordinary native speakers. The rough (but working!)
conversion tool is
https://chromium-review.googlesource.com/c/466727/1/rewrite_expectassert_eq.py,
and “git cl format” cleaned up its output.
EXPECT_NE and ASSERT_NE never had a preferred ordering. gtest never made
a judgment that one side or the other needed to provide an “unexpected”
value. Consequently, some code used (unexpected, actual) while other
code used (actual, unexpected). For consistency with the new EXPECT_EQ
and ASSERT_EQ usage, as well as consistency with CHECK_NE and DCHECK_NE,
this change also updates these use sites to (actual, unexpected) where
one side can be called “unexpected” as, for example, std::string::npos
can be. Unfortunately, this portion was a manual conversion.
References:
https://github.com/google/googletest/blob/master/googletest/docs/Primer.md#binary-comparison
https://github.com/google/googletest/commit/77d6b173380332b1c1bc540532641f410ec82d65
https://github.com/google/googletest/pull/713
Change-Id: I978fef7c94183b8b1ef63f12f5ab4d6693626be3
Reviewed-on: https://chromium-review.googlesource.com/466727
Reviewed-by: Scott Graham <scottmg@chromium.org>
2017-04-04 00:35:21 -04:00
|
|
|
|
EXPECT_EQ(output->at(output->size() - 1), '\n');
|
2014-08-15 22:33:14 -07:00
|
|
|
|
output->resize(output->size() - 1);
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
|
2020-09-01 17:09:37 -04:00
|
|
|
|
TEST(MacUtil, MacOSVersionComponents) {
|
2014-08-15 22:33:14 -07:00
|
|
|
|
int major;
|
|
|
|
|
int minor;
|
|
|
|
|
int bugfix;
|
|
|
|
|
std::string build;
|
|
|
|
|
std::string version_string;
|
2023-06-02 13:22:52 +03:00
|
|
|
|
ASSERT_TRUE(
|
|
|
|
|
MacOSVersionComponents(&major, &minor, &bugfix, &build, &version_string));
|
2020-09-01 17:09:37 -04:00
|
|
|
|
|
|
|
|
|
EXPECT_GE(major, 10);
|
|
|
|
|
EXPECT_LE(major, 99);
|
|
|
|
|
EXPECT_GE(minor, 0);
|
|
|
|
|
EXPECT_LE(minor, 99);
|
|
|
|
|
EXPECT_GE(bugfix, 0);
|
|
|
|
|
EXPECT_LE(bugfix, 99);
|
2014-08-15 22:33:14 -07:00
|
|
|
|
|
|
|
|
|
std::string version;
|
|
|
|
|
if (bugfix) {
|
|
|
|
|
version = base::StringPrintf("%d.%d.%d", major, minor, bugfix);
|
|
|
|
|
} else {
|
|
|
|
|
// 10.x.0 releases report their version string as simply 10.x.
|
|
|
|
|
version = base::StringPrintf("%d.%d", major, minor);
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
std::string expected_product_version;
|
2014-10-09 15:08:54 -04:00
|
|
|
|
ASSERT_NO_FATAL_FAILURE(
|
|
|
|
|
SwVers(@"-productVersion", &expected_product_version));
|
2014-08-15 22:33:14 -07:00
|
|
|
|
|
test: Use (actual, [un]expected) in gtest {ASSERT,EXPECT}_{EQ,NE}
gtest used to require (expected, actual) ordering for arguments to
EXPECT_EQ and ASSERT_EQ, and in failed test assertions would identify
each side as “expected” or “actual.” Tests in Crashpad adhered to this
traditional ordering. After a gtest change in February 2016, it is now
agnostic with respect to the order of these arguments.
This change mechanically updates all uses of these macros to (actual,
expected) by reversing them. This provides consistency with our use of
the logging CHECK_EQ and DCHECK_EQ macros, and makes for better
readability by ordinary native speakers. The rough (but working!)
conversion tool is
https://chromium-review.googlesource.com/c/466727/1/rewrite_expectassert_eq.py,
and “git cl format” cleaned up its output.
EXPECT_NE and ASSERT_NE never had a preferred ordering. gtest never made
a judgment that one side or the other needed to provide an “unexpected”
value. Consequently, some code used (unexpected, actual) while other
code used (actual, unexpected). For consistency with the new EXPECT_EQ
and ASSERT_EQ usage, as well as consistency with CHECK_NE and DCHECK_NE,
this change also updates these use sites to (actual, unexpected) where
one side can be called “unexpected” as, for example, std::string::npos
can be. Unfortunately, this portion was a manual conversion.
References:
https://github.com/google/googletest/blob/master/googletest/docs/Primer.md#binary-comparison
https://github.com/google/googletest/commit/77d6b173380332b1c1bc540532641f410ec82d65
https://github.com/google/googletest/pull/713
Change-Id: I978fef7c94183b8b1ef63f12f5ab4d6693626be3
Reviewed-on: https://chromium-review.googlesource.com/466727
Reviewed-by: Scott Graham <scottmg@chromium.org>
2017-04-04 00:35:21 -04:00
|
|
|
|
EXPECT_EQ(version, expected_product_version);
|
2014-08-15 22:33:14 -07:00
|
|
|
|
|
|
|
|
|
std::string expected_build_version;
|
2014-10-09 15:08:54 -04:00
|
|
|
|
ASSERT_NO_FATAL_FAILURE(SwVers(@"-buildVersion", &expected_build_version));
|
2014-08-15 22:33:14 -07:00
|
|
|
|
|
test: Use (actual, [un]expected) in gtest {ASSERT,EXPECT}_{EQ,NE}
gtest used to require (expected, actual) ordering for arguments to
EXPECT_EQ and ASSERT_EQ, and in failed test assertions would identify
each side as “expected” or “actual.” Tests in Crashpad adhered to this
traditional ordering. After a gtest change in February 2016, it is now
agnostic with respect to the order of these arguments.
This change mechanically updates all uses of these macros to (actual,
expected) by reversing them. This provides consistency with our use of
the logging CHECK_EQ and DCHECK_EQ macros, and makes for better
readability by ordinary native speakers. The rough (but working!)
conversion tool is
https://chromium-review.googlesource.com/c/466727/1/rewrite_expectassert_eq.py,
and “git cl format” cleaned up its output.
EXPECT_NE and ASSERT_NE never had a preferred ordering. gtest never made
a judgment that one side or the other needed to provide an “unexpected”
value. Consequently, some code used (unexpected, actual) while other
code used (actual, unexpected). For consistency with the new EXPECT_EQ
and ASSERT_EQ usage, as well as consistency with CHECK_NE and DCHECK_NE,
this change also updates these use sites to (actual, unexpected) where
one side can be called “unexpected” as, for example, std::string::npos
can be. Unfortunately, this portion was a manual conversion.
References:
https://github.com/google/googletest/blob/master/googletest/docs/Primer.md#binary-comparison
https://github.com/google/googletest/commit/77d6b173380332b1c1bc540532641f410ec82d65
https://github.com/google/googletest/pull/713
Change-Id: I978fef7c94183b8b1ef63f12f5ab4d6693626be3
Reviewed-on: https://chromium-review.googlesource.com/466727
Reviewed-by: Scott Graham <scottmg@chromium.org>
2017-04-04 00:35:21 -04:00
|
|
|
|
EXPECT_EQ(build, expected_build_version);
|
2014-08-15 22:33:14 -07:00
|
|
|
|
|
|
|
|
|
std::string expected_product_name;
|
2014-10-09 15:08:54 -04:00
|
|
|
|
ASSERT_NO_FATAL_FAILURE(SwVers(@"-productName", &expected_product_name));
|
2014-08-15 22:33:14 -07:00
|
|
|
|
|
|
|
|
|
// Look for a space after the product name in the complete version string.
|
|
|
|
|
expected_product_name += ' ';
|
test: Use (actual, [un]expected) in gtest {ASSERT,EXPECT}_{EQ,NE}
gtest used to require (expected, actual) ordering for arguments to
EXPECT_EQ and ASSERT_EQ, and in failed test assertions would identify
each side as “expected” or “actual.” Tests in Crashpad adhered to this
traditional ordering. After a gtest change in February 2016, it is now
agnostic with respect to the order of these arguments.
This change mechanically updates all uses of these macros to (actual,
expected) by reversing them. This provides consistency with our use of
the logging CHECK_EQ and DCHECK_EQ macros, and makes for better
readability by ordinary native speakers. The rough (but working!)
conversion tool is
https://chromium-review.googlesource.com/c/466727/1/rewrite_expectassert_eq.py,
and “git cl format” cleaned up its output.
EXPECT_NE and ASSERT_NE never had a preferred ordering. gtest never made
a judgment that one side or the other needed to provide an “unexpected”
value. Consequently, some code used (unexpected, actual) while other
code used (actual, unexpected). For consistency with the new EXPECT_EQ
and ASSERT_EQ usage, as well as consistency with CHECK_NE and DCHECK_NE,
this change also updates these use sites to (actual, unexpected) where
one side can be called “unexpected” as, for example, std::string::npos
can be. Unfortunately, this portion was a manual conversion.
References:
https://github.com/google/googletest/blob/master/googletest/docs/Primer.md#binary-comparison
https://github.com/google/googletest/commit/77d6b173380332b1c1bc540532641f410ec82d65
https://github.com/google/googletest/pull/713
Change-Id: I978fef7c94183b8b1ef63f12f5ab4d6693626be3
Reviewed-on: https://chromium-review.googlesource.com/466727
Reviewed-by: Scott Graham <scottmg@chromium.org>
2017-04-04 00:35:21 -04:00
|
|
|
|
EXPECT_EQ(version_string.find(expected_product_name), 0u);
|
2014-08-15 22:33:14 -07:00
|
|
|
|
}
|
|
|
|
|
|
2020-09-01 17:09:37 -04:00
|
|
|
|
TEST(MacUtil, MacOSVersionNumber) {
|
|
|
|
|
// Make sure that MacOSVersionNumber() and MacOSVersionComponents() agree. The
|
|
|
|
|
// two have their own distinct implementations, and the latter was checked
|
|
|
|
|
// against sw_vers above.
|
|
|
|
|
int macos_version_number = MacOSVersionNumber();
|
|
|
|
|
EXPECT_GE(macos_version_number, 10'00'00);
|
|
|
|
|
EXPECT_LE(macos_version_number, 99'99'99);
|
|
|
|
|
|
2014-08-15 22:33:14 -07:00
|
|
|
|
int major;
|
|
|
|
|
int minor;
|
|
|
|
|
int bugfix;
|
|
|
|
|
std::string build;
|
|
|
|
|
std::string version_string;
|
2023-06-02 13:22:52 +03:00
|
|
|
|
ASSERT_TRUE(
|
|
|
|
|
MacOSVersionComponents(&major, &minor, &bugfix, &build, &version_string));
|
2014-08-15 22:33:14 -07:00
|
|
|
|
|
2020-09-01 17:09:37 -04:00
|
|
|
|
EXPECT_EQ(macos_version_number,
|
|
|
|
|
major * 1'00'00 + minor * 1'00 +
|
2020-09-09 22:35:13 -04:00
|
|
|
|
(macos_version_number >= 10'13'04 ? bugfix : 0));
|
2014-08-15 22:33:14 -07:00
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
TEST(MacUtil, MacModelAndBoard) {
|
|
|
|
|
// There’s not much that can be done to test these, so just make sure they’re
|
|
|
|
|
// not empty. The model could be compared against the parsed output of
|
|
|
|
|
// “system_profiler SPHardwareDataType”, but the board doesn’t show up
|
|
|
|
|
// anywhere other than the I/O Registry, and that’s exactly how
|
|
|
|
|
// MacModelAndBoard() gets the data, so it wouldn’t be a very useful test.
|
|
|
|
|
std::string model;
|
|
|
|
|
std::string board;
|
|
|
|
|
MacModelAndBoard(&model, &board);
|
|
|
|
|
|
|
|
|
|
EXPECT_FALSE(model.empty());
|
|
|
|
|
EXPECT_FALSE(board.empty());
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
} // namespace
|
2014-10-07 17:28:50 -04:00
|
|
|
|
} // namespace test
|
|
|
|
|
} // namespace crashpad
|