chi-dragonflies-2015 / faqrator

DBC Final Project for FAQrator

FAQrator

Description

FAQrator is a tool for creating dynamic ad-hoc FAQS for events like lectures, classes, projects, etc. Users can create topics, which will allow users to submit questions to be answered. The topic creator will be able to view the list of open questions and submit answers based on a secret edit page, which can be accessed by a generated key, so that they may be able to share list control with others. It will be possible to comment on both questions and answers, to stimulate dialogue between all participants.

System Requirements

• ruby 2.0.0p481
• rails 4.2.3
• PostgreSQL 9.4.1
• Internet Access
• Javascript Enabled
• A browser with HTML5

External APIs and Libraries

• Materialize
• ZeroClipboard
• Acts_as_Votable
• jquery
• friendly_id

Getting Started

Testing

use rspec

Schema

Contributors

• Henry Firth
• Lola Adekunle
• Matt Faliszek

faqrator's Issues

Capybara testing of comments

theres an issue where it wants creator to be defined, which it should be. lines 15 and 29 in comment feature spec. routes should be passing along creator variable correctly, and does so in manual testing. not the case in capybara however.

creator is a local variable for partials to specify whether it will display information for creators only when edit key is present.

Answer validation

We need to figure out a good way to handle a user submitting an empty answer

Questions Create Route doesn't cover validations

when we work on adding validations to the question model, we need to update the question#create route to use Question.new and Question.save.

Questions should be present and have a minimum length

random guest name not working

we might not care, but something with the integration of the comments with questions broke the random guest default if author is not provided.

testing slack integration!

this working?

Heroku setup

Get started early with the deployment so we can constantly check it.

probably should set up auto-deployment through travis--that seemed useful for the client project.

posting comments doesnt preserve creator status

so posting a comment works ajax-wise as a regular user. when you're a creator though, you won't be able to delete a post until you reload the page--the button thinks you're a normal user at that point.

deleting and upvoting expand collapsibles

Newly added questions break jquery

There are two things that do not happen on newly added questions:

1. Propagation is not stopped, meaning the collapsible expands after clicking the edit/delete buttons.
2. Clicking the edit button no longer triggers the modal from for editing an unanswered question.

duplicate IDs (oh no!)

I think some of our pages have duplicate IDs on HTML selectors

flashes and notifications

we need to get a unified structure for notices and flashes to be displayed and useful.

JS not on heroku!

oh no!

Capybara testing of AJAX

in the features testing of comments, attempting to post has a split test--whether its an AJAX call or not. if it is an AJAX call, the page should show the comment followed by "Just Now!" until its reloaded, rather than a formatted timestamp.

testing of routes shows that in manual testing, its functioning as an AJAX call (AJAXY and NOT AJAXY depending on the logic). Capybara however, is doing it as a not AJAX call.

Working theory is that its making the check immediately, and its failing, so its immediately calling the non-ajax option. Ideally it'd wait for the ajax call to complete, which may in theory solve it.

need a route to all users page

Coveralls Integration

Need a way to keep track of test coverage.

Travis Integration

We know its obnoxious, but we need to get it done.

show edit view when creator

currently going to a topic you own doesn't default to the edit view, have to type in /edit.