From bc41170675306601706f0c7b52aa6654e29bfe53 Mon Sep 17 00:00:00 2001
From: Kilian Hofmann <llego03@yahoo.com>
Date: Thu, 31 Mar 2016 20:17:47 +0200
Subject: [PATCH] Cleared tests

---
 FMC Planner 2Tests/FMC_Planner_2Tests.m     | 26 +++++++-----------
 FMC Planner 2UITests/FMC_Planner_2UITests.m | 30 +++++++++++----------
 2 files changed, 26 insertions(+), 30 deletions(-)

diff --git a/FMC Planner 2Tests/FMC_Planner_2Tests.m b/FMC Planner 2Tests/FMC_Planner_2Tests.m
index bf78b37..5e30b1a 100644
--- a/FMC Planner 2Tests/FMC_Planner_2Tests.m	
+++ b/FMC Planner 2Tests/FMC_Planner_2Tests.m	
@@ -6,6 +6,8 @@
 //  Copyright © 2016 Kilian Hofmann. All rights reserved.
 //
 
+#import "AppDelegate.h"
+#import "DropboxV2ObjC.h"
 #import <XCTest/XCTest.h>
 
 @interface FMC_Planner_2Tests : XCTestCase
@@ -14,26 +16,18 @@
 
 @implementation FMC_Planner_2Tests
 
-- (void)setUp {
+- (void)setUp
+{
     [super setUp];
-    // Put setup code here. This method is called before the invocation of each test method in the class.
+    // Put setup code here. This method is called before the invocation of each
+    // test method in the class.
 }
 
-- (void)tearDown {
-    // Put teardown code here. This method is called after the invocation of each test method in the class.
+- (void)tearDown
+{
+    // Put teardown code here. This method is called after the invocation of
+    // each test method in the class.
     [super tearDown];
 }
 
-- (void)testExample {
-    // This is an example of a functional test case.
-    // Use XCTAssert and related functions to verify your tests produce the correct results.
-}
-
-- (void)testPerformanceExample {
-    // This is an example of a performance test case.
-    [self measureBlock:^{
-        // Put the code you want to measure the time of here.
-    }];
-}
-
 @end
diff --git a/FMC Planner 2UITests/FMC_Planner_2UITests.m b/FMC Planner 2UITests/FMC_Planner_2UITests.m
index d20598f..2a7f2e3 100644
--- a/FMC Planner 2UITests/FMC_Planner_2UITests.m	
+++ b/FMC Planner 2UITests/FMC_Planner_2UITests.m	
@@ -14,27 +14,29 @@
 
 @implementation FMC_Planner_2UITests
 
-- (void)setUp {
+- (void)setUp
+{
     [super setUp];
-    
-    // Put setup code here. This method is called before the invocation of each test method in the class.
-    
+
+    // Put setup code here. This method is called before the invocation of each
+    // test method in the class.
+
     // In UI tests it is usually best to stop immediately when a failure occurs.
     self.continueAfterFailure = NO;
-    // UI tests must launch the application that they test. Doing this in setup will make sure it happens for each test method.
+    // UI tests must launch the application that they test. Doing this in setup
+    // will make sure it happens for each test method.
     [[[XCUIApplication alloc] init] launch];
-    
-    // In UI tests it’s important to set the initial state - such as interface orientation - required for your tests before they run. The setUp method is a good place to do this.
+
+    // In UI tests it’s important to set the initial state - such as interface
+    // orientation - required for your tests before they run. The setUp method
+    // is a good place to do this.
 }
 
-- (void)tearDown {
-    // Put teardown code here. This method is called after the invocation of each test method in the class.
+- (void)tearDown
+{
+    // Put teardown code here. This method is called after the invocation of
+    // each test method in the class.
     [super tearDown];
 }
 
-- (void)testExample {
-    // Use recording to get started writing UI tests.
-    // Use XCTAssert and related functions to verify your tests produce the correct results.
-}
-
 @end