mirror of
https://github.com/wpilibsuite/allwpilib
synced 2026-06-30 02:31:44 +00:00
I'm not 100% sure whether we want these, but they are a quick find and replace to do. Basically, there are two primary things that we have done this summer that break existing user code: -Changing GetInstance() calls to return references instead of pointers. This forces users to change from doing something like LiveWindow::GetInstance()->AddSensor() to LiveWindow::GetInstance().AddSensor(). -Making PIDGet() and related calls const, forcing users to change the function signatures wherever they override them. The GetInstance() calls don't really matter to me either way, especially since there are no real ownership issues going on there, unlike the rest of the smart pointer-related changes. For the const stuff, it is certainly more correct to mandate that user PIDGet() functions be const and the such, but at the same time, I'm not sure that there is any strong need for it, and the errors generated are not the most helpful. While this wouldn't necessarily be an issue for more experienced teams or completely new teams (who don't have any old code to be reusing), it may cause issues for more average teams who aren't familiar with the intricacies of C++ anything. Change-Id: I6e7007982069292ea70e6d0fc8ca40203340df1b
47 lines
1.7 KiB
C++
47 lines
1.7 KiB
C++
/*----------------------------------------------------------------------------*/
|
|
/* Copyright (c) FIRST 2014. All Rights Reserved. */
|
|
/* Open Source Software - may be modified and shared by FRC teams. The code */
|
|
/* must be accompanied by the FIRST BSD license file in the root directory of */
|
|
/* the project. */
|
|
/*----------------------------------------------------------------------------*/
|
|
|
|
#include <DriverStation.h>
|
|
#include <LiveWindow/LiveWindow.h>
|
|
#include <Timer.h>
|
|
#include "gtest/gtest.h"
|
|
|
|
class TestEnvironment : public testing::Environment {
|
|
bool m_alreadySetUp = false;
|
|
|
|
public:
|
|
virtual void SetUp() override {
|
|
/* Only set up once. This allows gtest_repeat to be used to
|
|
automatically repeat tests. */
|
|
if (m_alreadySetUp) return;
|
|
m_alreadySetUp = true;
|
|
|
|
if (!HALInitialize()) {
|
|
std::cerr << "FATAL ERROR: HAL could not be initialized" << std::endl;
|
|
exit(-1);
|
|
}
|
|
|
|
/* This sets up the network communications library to enable the driver
|
|
station. After starting network coms, it will loop until the driver
|
|
station returns that the robot is enabled, to ensure that tests
|
|
will be able to run on the hardware. */
|
|
HALNetworkCommunicationObserveUserProgramStarting();
|
|
LiveWindow::GetInstance()->SetEnabled(false);
|
|
|
|
std::cout << "Waiting for enable" << std::endl;
|
|
|
|
while (!DriverStation::GetInstance().IsEnabled()) {
|
|
Wait(0.1);
|
|
}
|
|
}
|
|
|
|
virtual void TearDown() override {}
|
|
};
|
|
|
|
testing::Environment *const environment =
|
|
testing::AddGlobalTestEnvironment(new TestEnvironment);
|