makersacademy · AlexBuzea · Jun 12, 2023 · Jun 13, 2023 · Jun 13, 2023 · Jun 13, 2023
diff --git a/.DS_Store b/.DS_Store
diff --git a/README.md b/README.md
@@ -14,7 +14,7 @@ It uses:
 
 ## Card wall
 
-REPLACE THIS TEXT WITH A LINK TO YOUR CARD WALL
+https://trello.com/invite/b/Fv5Elopq/ATTI7a7e4a5260b33e9bf40ad2a5da74932bF6FF7822/acebook-team-neutral
 
 ## Quickstart
 

diff --git a/Test Documents/Acebook-Test-Plan.md b/Test Documents/Acebook-Test-Plan.md
@@ -0,0 +1,83 @@
+# Acebook Test Plan
+
+## Objective
+
+This test plan intends to outline the testing that will be performed on the Acebook code that is being developed by our team.
+It will aim to highlight potential bugs in the software and provide information on their severity and priority prior to deployment.
+
+The Acebook website is a piece of software that aims to allow a user to:
+  - Sign up 
+  - Log in 
+  - Edit and update their profile
+  - Create and publish a post
+  - View a list of users that they can send a friend request to
+  - Approve and deny friend requests
+  - View a list of their friends
+  - View feed
+  - Comment and like posts from other users
+  - Log out
+
+
+## Scope of testing
+
+We are going to test all of the main pieces of functionality from a users perspective. We will also include some validation checking for areas such as email addresses and user passwords. In addition we will be testing the database functionaility for items such as unique user ID's and the integration between each database. 
+
+## Test environment
+
+These test sessions will be conducted in VSCode as well as multiple modern browsers starting with Chrome and moving to Firefox.
+
+## Test Team
+
+The test team consists of 4 testers.
+
+- Sean Wright
+- James Turnbull
+- Chris Hall
+- Patrick Hagan
+
+## Features to be tested
+
+- User sign up and field validity checks
+- Login
+- Log out
+- Page navigation (once logged in)
+- Duplicate user accounts (blocked)
+- Users can create a post (can consist of text and/or pictures)
+- Editing profile
+- Check that a user can add a profile picture
+- Check name and picture appears beside their own posts
+- Sending friend requests
+- Approving/denying a friend request 
+- View list of friends
+- View list of users they may know
+- Be able to comment on a post in their feed
+- Be able to like a post in their feed and view the number of likes for that post
+
+## Assumptions
+
+During these tests certain assumptions will be made to make testing more effective and efficient. These assumptions are as follows:
+
+- Only users logged in will be able to make a post
+- The language will be English
+- 
+
+## Defect management
+
+When a defect is found it will be noted and a bug report will be created containing the details of the issue as well as the steps to reproduce. These will then be placed onto the teams Trello board in the 'Reviewed - Needs action' list. From here it will be picked up by the development team and then resubmitted for review by the test team. Once the tests have been conducted and the team is happy the task will be placed into the 'Done' list.
+
+## Risks
+
+| Risk | Mitigation |
+| ---- | ---------- |
+| Friction within the team. | Talk through issues/use coaches where needed. |
+| Recent intermittent internet access in testers home. | Use of hot spot if necessary. |
+| Time limit not allowing for all features to be tested. | Limit straying or chasing rabit holes. |
+| Lack of knowledge of language and codebase for testers. | Use coaches/devs and the internet to upskill |
+
+## Exit criteria
+
+The project will be deemed completed once all of the tasks on the Trello board are placed into done or when the time limit has been reached (02/06/2023).
+
+
+
+
diff --git a/Test Documents/Screenshot 2023-06-20 at 15.50.22.png b/Test Documents/Screenshot 2023-06-20 at 15.50.22.png
diff --git a/Test Documents/Screenshot 2023-06-20 at 15.50.30-1.png b/Test Documents/Screenshot 2023-06-20 at 15.50.30-1.png
diff --git a/Test Documents/Screenshot 2023-06-20 at 15.50.30.png b/Test Documents/Screenshot 2023-06-20 at 15.50.30.png
diff --git a/Test Documents/Screenshot 2023-06-20 at 15.58.27.png b/Test Documents/Screenshot 2023-06-20 at 15.58.27.png
diff --git a/Test Documents/Screenshot 2023-06-20 at 15.58.42.png b/Test Documents/Screenshot 2023-06-20 at 15.58.42.png
diff --git a/Test Documents/notes.md b/Test Documents/notes.md
@@ -0,0 +1,24 @@
+# Exploratory Testing Notes
+
+## Landing Page
+
+## Sign-up Page
+
+- Validation - should numbers be allowed in first name and second name? I believe it's standard to disallow the use of number
+- Validation - Should the names be allowed with any capitalization and then be manipulated to always follow capital first letter structure?
+- Validation - Check database for duplicate emails
+- Feature suggestion - After signing up successfully, an alert pops up after the redirect to the login page that lets the user know their account was created successfully
+- HTML - Consistency with element tagging - Title has a class on home page but not on sign up
+
+## Single Post
+
+- Validation on commenting - Currently can submit empty comment
+- Feature Recommendation - User can remove their like from a post
+
+### CSS
+
+- Fixed size for the comment text box?
+
+## Profile
+
+- BUG - Name coming through as 'Name' instead of user name
diff --git a/Test Documents/test_cases.md b/Test Documents/test_cases.md
@@ -0,0 +1,59 @@
+## PAGES:
+1 - Homepage/login
+2 - Sign up
+3 - Feed
+4 - Profile
+5 - Users
+
+
+## TEST CASES:
+
+*** 1 ***
+
+Homepage:
+- Title is visible and reads 'Acebook'
+- Check login fields on page 
+- Check sign up button and redirects to sign up page
+
+Login:
+- Error if username or password wrong 
+- Log in with correct details and redirected to feed page
+
+
+*** 2 ***
+
+- Username (email) & password validation checks (Unit test maybe)
+- After succesful sign up returned to homepage, possibly with confirmation message 
+- Error messages if details incorrect
+- Button to return to homepage
+
+
+*** 3 ***
+
+- User can submit a post
+- User can like a post
+- User can react/comment on a post
+- Likes are shown
+- Username is shown for the post 
+- Posts are in chronological order 
+- All posts are shown
+- User can edit/delete a post (nice-to-have)
+- Hide certain user posts (nice-to-have)
+
+
+*** 4 ***
+
+- User can upload/edit profile picture
+- Users friends can be seen 
+- User can edit/update personal details
+- User can't view other users password/personal info
+- Users posts are viewable
+- Button to feed/logout/other profiles (possibly) are in navbar
+
+
+*** 5 ***
+
+- View all users
+- Add friends
+- Remove friends 
+- Pending requests 
diff --git a/app.js b/app.js
@@ -10,6 +10,11 @@ const homeRouter = require("./routes/home");
 const postsRouter = require("./routes/posts");
 const sessionsRouter = require("./routes/sessions");
 const usersRouter = require("./routes/users");
+const profileRouter = require("./routes/profile");
+const commentsRouter = require("./routes/posts");
+const { handlebars } = require("hbs");
+const moment = require("./public/javascripts/moment.min");
+
 
 const app = express();
 
@@ -25,54 +30,63 @@ app.use(express.static(path.join(__dirname, "public")));
 app.use(methodOverride("_method"));
 
 app.use(
-  session({
-    key: "user_sid",
-    secret: "super_secret",
-    resave: false,
-    saveUninitialized: false,
-    cookie: {
-      expires: 600000,
-    },
-  })
+	session({
+		key: "user_sid",
+		secret: "super_secret",
+		resave: false,
+		saveUninitialized: false,
+		cookie: {
+			expires: 600000,
+		},
+	})
 );
 
-// clear the cookies after user logs out
+// clear the cookies and session after user logs out
 app.use((req, res, next) => {
-  if (req.cookies.user_sid && !req.session.user) {
-    res.clearCookie("user_sid");
-  }
-  next();
+	if (req.cookies.user_sid && !req.session.user) {
+		res.clearCookie("user_sid");
+		req.session.friendRequestSent = null; // Clear the friendRequestSent value
+	}
+	next();
 });
 
 // middleware function to check for logged-in users
 const sessionChecker = (req, res, next) => {
-  if (!req.session.user && !req.cookies.user_sid) {
-    res.redirect("/sessions/new");
-  } else {
-    next();
-  }
+	if (!req.session.user && !req.cookies.user_sid) {
+		res.redirect("/sessions/new");
+	} else {
+		next();
+	}
 };
 
 // route setup
 app.use("/", homeRouter);
 app.use("/posts", sessionChecker, postsRouter);
 app.use("/sessions", sessionsRouter);
 app.use("/users", usersRouter);
+app.use("/profile", profileRouter);
+app.use("/:postId", sessionChecker, postsRouter);
+app.use("/:postId/comments", sessionChecker, commentsRouter);
+app.use("/:postId/like", sessionChecker, postsRouter);
+app.use("/posts/new", sessionChecker, postsRouter);
 
 // catch 404 and forward to error handler
 app.use((req, res, next) => {
-  next(createError(404));
+	next(createError(404));
 });
 
 // error handler
 app.use((err, req, res) => {
-  // set locals, only providing error in development
-  res.locals.message = err.message;
-  res.locals.error = req.app.get("env") === "development" ? err : {};
+	// set locals, only providing error in development
+	res.locals.message = err.message;
+	res.locals.error = req.app.get("env") === "development" ? err : {};
 
-  // render the error page
-  res.status(err.status || 500);
-  res.render("error");
+	// render the error page
+	res.status(err.status || 500);
+	res.render("error");
 });
 
+handlebars.registerHelper("timeAgo", (date) => moment(date).fromNow());
+
 module.exports = app;
+module.exports.sessionChecker = sessionChecker;