Test

Type: Test

Author: cgbosse

__test__/client_daysTillTrip.test.js

@@ -0,0 +1,24 @@
+ // Import the js file to test
+ import { daysTillTrip } from "../src/client/js/daysTillTrip"
+
+describe("Testing the generation of days indication", () => {
+    test("Testing the formCheck() function with an empty object response", () => {
+            // Define the input for the function, if any, in the form of variables/array
+            const input = "None Selected";
+            // Define the expected output, if any, in the form of variables/array
+            // The expect() function, in combination with a Jest matcher, is used to check if the function produces the expected output
+            // The general syntax is `expect(myFunction(arg1, arg2, ...)).toEqual(expectedValue);`, where `toEqual()` is a matcher
+            expect(daysTillTrip(input)).toBe(0);
+            }
+        );
+        test("Testing the formCheck() function with the date 2029/12/31", () => {
+            // Define the input for the function, if any, in the form of variables/array
+            const input = "2029/12/31";
+            // Define the expected output, if any, in the form of variables/array
+            // The expect() function, in combination with a Jest matcher, is used to check if the function produces the expected output
+            // The general syntax is `expect(myFunction(arg1, arg2, ...)).toEqual(expectedValue);`, where `toEqual()` is a matcher
+            expect(daysTillTrip(input)).toBeGreaterThan(0);
+            }
+        );
+    }
+);

__test__/client_formCheck.test.js

@@ -0,0 +1,12 @@
+ // Import the js file to test
+ import { formCheck } from "../src/client/js/formCheck"
+
+describe("Testing whether the fields are filled out correctly", () => {
+    test("Testing the formCheck() function", () => {
+            // Define the input for the function, if any, in the form of variables/array
+            const input = "";
+            // Define the expected output, if any, in the form of variables/array
+            // The expect() function, in combination with a Jest matcher, is used to check if the function produces the expected output
+            // The general syntax is `expect(myFunction(arg1, arg2, ...)).toEqual(expectedValue);`, where `toEqual()` is a matcher
+            expect(formCheck(input)).toBeTruthy();
+})});

__test__/server_consultTrip.test.js

@@ -0,0 +1,36 @@
+ // Import the js file to test
+ //import { consultTrip } from "../src/server/consultTrip"
+
+// --------------------------------consultTrip-------------------------------------
+// Import function from another js file in the same folder
+let consultTrip = require('./src/server/consultTrip.js');
+
+
+describe("Testing the consultTrip request sent from the client side to the server", () => {
+    test("Testing the consultTrip() function with a prepared object request", () => {
+            // Define the input for the function, if any, in the form of variables/array
+            const input = {
+                "tripId":"1"
+            };
+            
+            // Variables referred to during the test
+            const savedTrips = {
+                "1": {
+                    "test": "object"
+                }
+            };
+
+            // Define the expected output, if any, in the form of variables/array
+            const output = {
+                "1": {
+                    "test": "object"
+                }
+            };
+            
+            // The expect() function, in combination with a Jest matcher, is used to check if the function produces the expected output
+            // The general syntax is `expect(myFunction(arg1, arg2, ...)).toEqual(expectedValue);`, where `toEqual()` is a matcher
+            expect(consultTrip(input)).toMatchObject(output);
+            }
+        );
+    }
+);

documentation/UDACITY_Project_Rubric.md

@@ -40,63 +40,63 @@ The project should have a structure like the one shown below. All files shown mu
 
 ### Usability
 
--[] All features are usable across modern desktop and phone browsers.
--[] Ensure the HTML elements, eg. texts and buttons, are proportionate and readable in small screen devices.
+-[x] All features are usable across modern desktop and phone browsers.
+-[x] Ensure the HTML elements, eg. texts and buttons, are proportionate and readable in small screen devices.
 
 ### Styling
 
--[] Styling is set up in a logical way. 
--[] All interactive elements have hover states.
+-[x] Styling is set up in a logical way. 
+-[x] All interactive elements have hover states.
 
 ### HTML Structure
 
--[] HTML structure should be indented properly with classes and ID’s that make sense.
+-[x] HTML structure should be indented properly with classes and ID’s that make sense.
 
 ### Visual Design
 
--[] The design should clearly be different from the design used in projects 3 and 4.
+-[x] The design should clearly be different from the design used in projects 3 and 4.
 
 ## API and JS Integration
 
 ---
 
 ### src > server > server.js
 
--[] server.js file should be taken directly from passed project 3 with the addition of added member: value pairs and the required API keys.
+-[x] server.js file should be taken directly from passed project 3 with the addition of added member: value pairs and the required API keys.
 
 ### index.js
 
--[] src > client > index.js
--[] At least one function should be imported.
+-[x] src > client > index.js
+-[x] At least one function should be imported.
 -[] At least one event listener should be imported.
 (styles referenced in html/css)
 
 ### app.js
 
--[] src > client > js > app.js
--[] There should be URLS and API Keys for at least 3 APIs, including Geonames, Weatherbit, and Pixabay. You can feel free to use more than 3 APIs.
--[] There should be a primary object with placeholder member value pairs.
--[] There should be a primary function that is exported to index.js (index.js file should import the functions from other files).
+-[x] src > client > js > app.js
+-[x] There should be URLS and API Keys for at least 3 APIs, including Geonames, Weatherbit, and Pixabay. You can feel free to use more than 3 APIs.
+-[x] There should be a primary object with placeholder member value pairs.
+-[x] There should be a primary function that is exported to index.js (index.js file should import the functions from other files).
 
 ## Documentation
 
 ---
 
 ### README
 
--[] A README file is included detailing the app and all dependencies.
+-[x] A README file is included detailing the app and all dependencies.
 
 #### Other requirements
 
 -[x] The Readme file should have non-default text in it that is specific to this project. It doesn’t have to be thorough, but should have some basic info. Bonus points if correct markdown is used.
 
 ### Comments
 
--[] Comments are present and effectively explain longer code procedure when necessary.
+-[x] Comments are present and effectively explain longer code procedure when necessary.
 
 ### Code Quality
 
--[] Code is formatted with consistent, logical, and easy-to-read formatting as described in the Udacity JavaScript Style Guide.
+-[x] Code is formatted with consistent, logical, and easy-to-read formatting as described in the Udacity JavaScript Style Guide.
 
 ## Suggestions to Make Your Project Stand Out!
 
@@ -108,7 +108,7 @@ At least one of these is required, but the rest are great additional ways to fur
 -[] Pull in an image for the country from Pixabay API when the entered location brings up no results (good for obscure localities).
 -[] Allow user to add multiple destinations on the same trip.
 -[] Pull in weather for additional locations.
--[] Allow the user to add hotel and/or flight data.
+-[x] Allow the user to add hotel and/or flight data.
 -[] Multiple places to stay? Multiple flights?
 -[] Integrate the REST Countries API to pull in data for the country - being visited.
 -[] Allow the user to remove the trip.
@@ -117,6 +117,6 @@ At least one of these is required, but the rest are great additional ways to fur
 -[] Incorporate icons into forecast.
 -[] Allow user to Print their trip and/or export to PDF.
 -[] Allow the user to add a todo list and/or packing list for their trip.
--[] Allow the user to add additional trips (this may take some heavy reworking, but is worth the challenge).
+-[x] Allow the user to add additional trips (this may take some heavy reworking, but is worth the challenge).
 -[] Automatically sort additional trips by countdown.
 -[] Move expired trips to bottom/have their style change so it’s clear it’s expired.