Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(217)

Unified Diff: components/offline_pages/core/test_task.h

Issue 2359933007: [Offline pages] Introduces TaskQueue to serialize tasks that asynchronously access SQLStore (Closed)
Patch Set: Addressing feedback from Dmitry Created 4 years, 3 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View side-by-side diff with in-line comments
Download patch
« no previous file with comments | « components/offline_pages/core/task_unittest.cc ('k') | components/offline_pages/core/test_task.cc » ('j') | no next file with comments »
Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
Index: components/offline_pages/core/test_task.h
diff --git a/components/offline_pages/core/test_task.h b/components/offline_pages/core/test_task.h
new file mode 100644
index 0000000000000000000000000000000000000000..01e517f55925eac2dada0ac3cbc02890ea028c19
--- /dev/null
+++ b/components/offline_pages/core/test_task.h
@@ -0,0 +1,59 @@
+// Copyright 2016 The Chromium Authors. All rights reserved.
+// Use of this source code is governed by a BSD-style license that can be
+// found in the LICENSE file.
+
+#ifndef COMPONENTS_OFFLINE_PAGES_CORE_TEST_TASK_H_
+#define COMPONENTS_OFFLINE_PAGES_CORE_TEST_TASK_H_
+
+#include "components/offline_pages/core/task.h"
+
+namespace offline_pages {
+
+// Sample resource consumed by the task during execution. In this set of tests
+// used to provide the capability to continue the task.
+class ConsumedResource {
+ public:
+ ConsumedResource();
+ ~ConsumedResource();
+
+ void Step(const base::Closure& step_callback);
+ void CompleteStep();
+ bool HasNextStep() const { return !next_step_.is_null(); }
+
+ private:
+ base::Closure next_step_;
+};
+
+// Sample test task. This should not be used as a example of task implementation
+// with respect to callback safety. Otherwise it captures the idea of splitting
+// the work into multiple steps separated by potentially asynchronous calls
+// spanning multiple threads.
+//
+// For an implementation example of a task that covers problems better is
+// |offline_pages::ChangeRequestsStateTask|.
+class TestTask : public Task {
+ public:
+ enum class TaskState { NOT_STARTED, STEP_1, STEP_2, COMPLETED };
+
+ explicit TestTask(ConsumedResource* resource);
+ TestTask(ConsumedResource* resource, bool leave_early);
+ ~TestTask() override;
+
+ // Run is Step 1 in our case.
+ void Run() override;
+
+ void Step2();
+
+ void LastStep();
+
+ TaskState state() const { return state_; }
+
+ private:
+ ConsumedResource* resource_;
+ TaskState state_;
+ bool leave_early_;
+};
+
+} // namespace offline_pages
+
+#endif // COMPONENTS_OFFLINE_PAGES_CORE_TEST_TASK_H_
« no previous file with comments | « components/offline_pages/core/task_unittest.cc ('k') | components/offline_pages/core/test_task.cc » ('j') | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698