CSC/ECE 517 Fall 2016/E1662. UI issues/fixes: Difference between revisions

From Expertiza_Wiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 21: Line 21:
* Currently when admin/instructor tries to delete an assignment, there is no alert/confirmation shown. This is risky. We need to add a confirmation step to avoid losing data.
* Currently when admin/instructor tries to delete an assignment, there is no alert/confirmation shown. This is risky. We need to add a confirmation step to avoid losing data.


=== Issue Details ===
=== Issue#702 ===
 
Capturing Institution ID
Functional tests ensure that the functionalities of a software system are working as expected. To write our functional tests, we used the Capybara gem available for Ruby.
Capybara gem allows a user to test their web application through simulations.


Institution and Course has One-to-Many relationship wherein one institution may have many courses associated with it. In current system while creating new course user does not have any provision of selecting Institution. Hence we need to fix this issue.
=== Functional Tests Implementation ===
=== Functional Tests Implementation ===


Revision as of 00:06, 29 October 2016

UI Issues/Fixes

Background

Expertiza is an open source web application developed by students and faculty members of North Carolina State University. This portal is being used by both faculty members and students in order to carry out assignments. Typically following is the workflow of the system:

  • Faculty member adds students to a particular course. He also adds an assignment for the class.
  • Assignment has a specific deadline, review period and final submission.
  • Faculty members upload list of topics for the assignment.
  • Students have to bid for the topic or they can suggest their own topic.
  • At the end of the bidding process, students get a specific topic for the assignment.
  • Students can form the teams by sending out invitations to other students.
  • Students start working on the assignment and submit the assignment work before the initial submission date.
  • Every student then gets to review work submitted by at least one team. Student submit their feedback in the review.
  • Students then make the necessary changes as suggested by reviewer and submit the assignment before the final submission date.
  • Students are graded on the basis of their work and reviews.

Objective

The main objective this project is to fix the issues in the current system. The current system has following issues:

  • Historically courses were created without providing Institution ID. However now since data warehousing is storing Institution Id for a particular course hence even this application should do that.
  • If an assignment is completed, no one can sign up for topics or drop topics. Yet a completely blank "Actions" column on the signup sheet still appears. It would be better if the column did not appear.
  • Currently when admin/instructor tries to delete an assignment, there is no alert/confirmation shown. This is risky. We need to add a confirmation step to avoid losing data.

Issue#702

Capturing Institution ID

Institution and Course has One-to-Many relationship wherein one institution may have many courses associated with it. In current system while creating new course user does not have any provision of selecting Institution. Hence we need to fix this issue.

Functional Tests Implementation

Running the tests

The tests can be run on the terminal using the command: 

 rspec specfile.rb

Whether the test fails or succeeds, allows us to determine which parts of the system are functioning properly.

External Links

  1. link for forked repository
  2. Github link for original repository
  3. Github link for Capybara
Retrieved from "https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2016/E1662._UI_issues/fixes&oldid=103383"