UpdateManager: Do not schedule update checks if OOBE did not complete.
This abides by the current logic, as found in
UpdateCheckScheduler::StaticCheck(). New unit test added to verify this
behavior.
BUG=chromium:358269
TEST=Unit tests.
Change-Id: I747e8a59408d6b93ceea62ef741b36e09f937a08
Reviewed-on: https://chromium-review.googlesource.com/207241
Reviewed-by: Alex Deymo <deymo@chromium.org>
Tested-by: Gilad Arnold <garnold@chromium.org>
Commit-Queue: Gilad Arnold <garnold@chromium.org>
diff --git a/update_manager/fake_config_provider.h b/update_manager/fake_config_provider.h
index 373ff0a..fab01d1 100644
--- a/update_manager/fake_config_provider.h
+++ b/update_manager/fake_config_provider.h
@@ -15,13 +15,12 @@
public:
FakeConfigProvider() {}
- protected:
virtual FakeVariable<bool>* var_is_oobe_enabled() override {
return &var_is_oobe_enabled_;
}
private:
- FakeVariable<bool> var_is_oobe_enabled_{
+ FakeVariable<bool> var_is_oobe_enabled_{ // NOLINT(whitespace/braces)
"is_oobe_enabled", kVariableModeConst};
DISALLOW_COPY_AND_ASSIGN(FakeConfigProvider);