<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://wiki.expertiza.ncsu.edu/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Psabhyan</id>
	<title>Expertiza_Wiki - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://wiki.expertiza.ncsu.edu/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Psabhyan"/>
	<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=Special:Contributions/Psabhyan"/>
	<updated>2026-08-20T01:02:33Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.41.0</generator>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2016/E1662._UI_issues/fixes&amp;diff=104140</id>
		<title>CSC/ECE 517 Fall 2016/E1662. UI issues/fixes</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2016/E1662._UI_issues/fixes&amp;diff=104140"/>
		<updated>2016-10-31T18:55:15Z</updated>

		<summary type="html">&lt;p&gt;Psabhyan: /* How to Test this fix? */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= UI Issues/Fixes =&lt;br /&gt;
&lt;br /&gt;
=== Background ===&lt;br /&gt;
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:&lt;br /&gt;
* Faculty member adds students to a particular course. He also adds an assignment for the class.&lt;br /&gt;
* Assignment has a specific deadline, review period and final submission.&lt;br /&gt;
* Faculty members upload list of topics for the assignment.&lt;br /&gt;
* Students have to bid for the topic or they can suggest their own topic.&lt;br /&gt;
* At the end of the bidding process, students get a specific topic for the assignment.&lt;br /&gt;
* Students can form the teams by sending out invitations to other students.&lt;br /&gt;
* Students start working on the assignment and submit the assignment work before the initial submission date.&lt;br /&gt;
* Every student then gets to review work submitted by at least one team. Student submit their feedback in the review.&lt;br /&gt;
* Students then make the necessary changes as suggested by reviewer and submit the assignment before the final submission date.&lt;br /&gt;
* Students are graded on the basis of their work and reviews.&lt;br /&gt;
&lt;br /&gt;
=== Objective ===&lt;br /&gt;
The main objective this project is to fix the issues in the current system. The current system has following issues:&lt;br /&gt;
&lt;br /&gt;
* 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.&lt;br /&gt;
* If an assignment is completed, no one can sign up for topics or drop topics. Yet a completely blank &amp;quot;Actions&amp;quot; column on the signup sheet still appears. It would be better if the column did not appear.&lt;br /&gt;
* 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.&lt;br /&gt;
=== Issues ===&lt;br /&gt;
==== Issue#702 ====&lt;br /&gt;
===== How was this Issue Fixed? =====&lt;br /&gt;
Capturing Institution ID&lt;br /&gt;
&lt;br /&gt;
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. Following basic changes are required in order to fix this issue.&lt;br /&gt;
* Ensure that relationship exists between Course and Institution model classes.&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
# Establishing relationship between Course and Institution&lt;br /&gt;
class Institution &amp;lt; ActiveRecord::Base&lt;br /&gt;
  has_many :courses, dependent: :destroy&lt;br /&gt;
end&lt;br /&gt;
&lt;br /&gt;
class Course &amp;lt; ActiveRecord::Base&lt;br /&gt;
  belongs_to :institution, class_name: 'Institution', foreign_key: 'instituition_id'&lt;br /&gt;
end&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* Add a dropdown list in Course creation form so that user can select institution from the available options.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
&amp;lt;!--Adding a field so that user can select institution from the list--&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;&amp;lt;label for=&amp;quot;course_institutions_id&amp;quot;&amp;gt;Institution Name&amp;lt;/label&amp;gt;&amp;lt;br/&amp;gt;&lt;br /&gt;
  &amp;lt;%= select_tag :'institutions_id', options_from_collection_for_select(Institution.where.not(:name=&amp;gt;nil), 'id', 'name'), :include_blank =&amp;gt; &amp;quot;Please select...&amp;quot;,:required=&amp;gt;true %&amp;gt;&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* Ensure that the id for the selected institution is sent as a parameter along with other parameters back to controller.&lt;br /&gt;
* Once we receive all the data in controller Institution id should be saved in course table.&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
 @course = Course.new(name: params[:course][:name], directory_path: &lt;br /&gt;
params[:course][:directory_path], info: params[:course][:info], &lt;br /&gt;
institutions_id: params[:institutions_id], private: params[:course][:private])&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===== How to Test this fix? =====&lt;br /&gt;
* User should login to expertiza using Instructor's credentials.&lt;br /&gt;
* Go to Manage Courses&lt;br /&gt;
* Click on New Course button so as to open form for it.&lt;br /&gt;
* Fill up the form. you can see new field added as Institution Name. This is a drop down list which has list of Institutions.&lt;br /&gt;
* User has to select one of these institutions. If user tries to go ahead without selecting this then he will get an alert flash saying this is a required field.&lt;br /&gt;
* Once an institution is selected user can click on Create button to submit the form.&lt;br /&gt;
* Institution Id would be saved in database record against this particular entry of course in Course table. User can verify this by accessing Course table in the database. &lt;br /&gt;
==== Issue#316 ====&lt;br /&gt;
===== How was this Issue Fixed? =====&lt;br /&gt;
When student open sign up sheet for the Finished projects, he should not be able to take any actions for that assignment and hence Actions column should be hidden to him. For fixing this bug, we had to make following changes into sign_up_sheet/_table_line.html.erb.&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
&amp;lt;%if !@assignment.get_current_stage.eql?&amp;quot;Finished&amp;quot;%&amp;gt;&lt;br /&gt;
  &amp;lt;td align=&amp;quot;center&amp;quot;&amp;gt;&lt;br /&gt;
    &amp;lt;%= render :partial =&amp;gt; '/sign_up_sheet/actions', &lt;br /&gt;
    :locals =&amp;gt; {:i=&amp;gt;i,:topic=&amp;gt;topic, :is_suggested_topic=&amp;gt;is_suggested_topic ||= false} %&amp;gt;&lt;br /&gt;
  &amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;%end%&amp;gt;&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===== How to Test this fix? =====&lt;br /&gt;
* Login to expertiza using student credentials&lt;br /&gt;
* Go to assignment tab&lt;br /&gt;
* Look for the assignments which have current stage as &amp;quot;Finished&amp;quot;&lt;br /&gt;
* Go to that assignment and open sign-up sheet.&lt;br /&gt;
* You should not be able to see column Activities. If you don't see this column then the test is successful.&lt;br /&gt;
&lt;br /&gt;
==== Issue#295 ====&lt;br /&gt;
===== How was this Issue Fixed? =====&lt;br /&gt;
When instructor clicks on delete button to delete courses/assignment, It gets deleted without confirming it. System should ask for confirmation whether to go ahead with deletion or not. We had to make following changes in _shared_action.html.erb&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
  &amp;lt;%= link_to image_tag('/assets/tree_view/delete-icon-24.png', :title =&amp;gt; 'Delete ' + model.downcase),&lt;br /&gt;
      { :controller =&amp;gt; controller, :action=&amp;gt;'delete', :id =&amp;gt; node.node_object_id , :data =&amp;gt; {:confirm =&amp;gt; 'Are you sure you want to delete?'}},&lt;br /&gt;
      { :title =&amp;gt; 'Delete ' + model.downcase } %&amp;gt;&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===== How to Test this fix? =====&lt;br /&gt;
* Login to Expertiza as an Instructor.&lt;br /&gt;
* Go to manage assignment page.&lt;br /&gt;
* Try deleting an assignment by clicking on an image from the activities column.&lt;br /&gt;
* When delete button is clicked, system should ask for confirmation message whether you really want to delete or not.&lt;br /&gt;
* If you select yes then that assignment should be deleted. Otherwise if selected no then that assignment should not be deleted.&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
1. https://github.com/expertiza/expertiza - Github link for original repository&lt;br /&gt;
&lt;br /&gt;
2. https://github.com/psabhyan/expertiza.git - Github Repository code for the updated code&lt;/div&gt;</summary>
		<author><name>Psabhyan</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2016/E1662._UI_issues/fixes&amp;diff=104139</id>
		<title>CSC/ECE 517 Fall 2016/E1662. UI issues/fixes</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2016/E1662._UI_issues/fixes&amp;diff=104139"/>
		<updated>2016-10-31T18:52:17Z</updated>

		<summary type="html">&lt;p&gt;Psabhyan: /* How to Test this fix? */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= UI Issues/Fixes =&lt;br /&gt;
&lt;br /&gt;
=== Background ===&lt;br /&gt;
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:&lt;br /&gt;
* Faculty member adds students to a particular course. He also adds an assignment for the class.&lt;br /&gt;
* Assignment has a specific deadline, review period and final submission.&lt;br /&gt;
* Faculty members upload list of topics for the assignment.&lt;br /&gt;
* Students have to bid for the topic or they can suggest their own topic.&lt;br /&gt;
* At the end of the bidding process, students get a specific topic for the assignment.&lt;br /&gt;
* Students can form the teams by sending out invitations to other students.&lt;br /&gt;
* Students start working on the assignment and submit the assignment work before the initial submission date.&lt;br /&gt;
* Every student then gets to review work submitted by at least one team. Student submit their feedback in the review.&lt;br /&gt;
* Students then make the necessary changes as suggested by reviewer and submit the assignment before the final submission date.&lt;br /&gt;
* Students are graded on the basis of their work and reviews.&lt;br /&gt;
&lt;br /&gt;
=== Objective ===&lt;br /&gt;
The main objective this project is to fix the issues in the current system. The current system has following issues:&lt;br /&gt;
&lt;br /&gt;
* 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.&lt;br /&gt;
* If an assignment is completed, no one can sign up for topics or drop topics. Yet a completely blank &amp;quot;Actions&amp;quot; column on the signup sheet still appears. It would be better if the column did not appear.&lt;br /&gt;
* 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.&lt;br /&gt;
=== Issues ===&lt;br /&gt;
==== Issue#702 ====&lt;br /&gt;
===== How was this Issue Fixed? =====&lt;br /&gt;
Capturing Institution ID&lt;br /&gt;
&lt;br /&gt;
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. Following basic changes are required in order to fix this issue.&lt;br /&gt;
* Ensure that relationship exists between Course and Institution model classes.&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
# Establishing relationship between Course and Institution&lt;br /&gt;
class Institution &amp;lt; ActiveRecord::Base&lt;br /&gt;
  has_many :courses, dependent: :destroy&lt;br /&gt;
end&lt;br /&gt;
&lt;br /&gt;
class Course &amp;lt; ActiveRecord::Base&lt;br /&gt;
  belongs_to :institution, class_name: 'Institution', foreign_key: 'instituition_id'&lt;br /&gt;
end&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* Add a dropdown list in Course creation form so that user can select institution from the available options.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
&amp;lt;!--Adding a field so that user can select institution from the list--&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;&amp;lt;label for=&amp;quot;course_institutions_id&amp;quot;&amp;gt;Institution Name&amp;lt;/label&amp;gt;&amp;lt;br/&amp;gt;&lt;br /&gt;
  &amp;lt;%= select_tag :'institutions_id', options_from_collection_for_select(Institution.where.not(:name=&amp;gt;nil), 'id', 'name'), :include_blank =&amp;gt; &amp;quot;Please select...&amp;quot;,:required=&amp;gt;true %&amp;gt;&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* Ensure that the id for the selected institution is sent as a parameter along with other parameters back to controller.&lt;br /&gt;
* Once we receive all the data in controller Institution id should be saved in course table.&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
 @course = Course.new(name: params[:course][:name], directory_path: &lt;br /&gt;
params[:course][:directory_path], info: params[:course][:info], &lt;br /&gt;
institutions_id: params[:institutions_id], private: params[:course][:private])&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===== How to Test this fix? =====&lt;br /&gt;
* User should login to expertiza using Instructor's credentials.&lt;br /&gt;
* Go to Manage Courses&lt;br /&gt;
* Click on New Course button so as to open form for it.&lt;br /&gt;
* Fill up the form. you can see new field added as Institution Name. This is a drop down list which has list of Institutions.&lt;br /&gt;
* User has to select one of these institutions. If user tries to go ahead without selecting this then he will get an alert flash saying this is a required field.&lt;br /&gt;
* Once an institution is selected user can click on Create button to submit the form.&lt;br /&gt;
* Institution Id would be saved in database record against this particular entry of course in Course table. User can verify this by accessing Course table in the database. &lt;br /&gt;
==== Issue#316 ====&lt;br /&gt;
===== How was this Issue Fixed? =====&lt;br /&gt;
When student open sign up sheet for the Finished projects, he should not be able to take any actions for that assignment and hence Actions column should be hidden to him. For fixing this bug, we had to make following changes into sign_up_sheet/_table_line.html.erb.&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
&amp;lt;%if !@assignment.get_current_stage.eql?&amp;quot;Finished&amp;quot;%&amp;gt;&lt;br /&gt;
  &amp;lt;td align=&amp;quot;center&amp;quot;&amp;gt;&lt;br /&gt;
    &amp;lt;%= render :partial =&amp;gt; '/sign_up_sheet/actions', &lt;br /&gt;
    :locals =&amp;gt; {:i=&amp;gt;i,:topic=&amp;gt;topic, :is_suggested_topic=&amp;gt;is_suggested_topic ||= false} %&amp;gt;&lt;br /&gt;
  &amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;%end%&amp;gt;&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===== How to Test this fix? =====&lt;br /&gt;
* Login to expertiza using student credentials&lt;br /&gt;
* Go to assignment tab&lt;br /&gt;
* Look for the assignments which have current stage as &amp;quot;Finished&amp;quot;&lt;br /&gt;
* Go to that assignment and open sign-up sheet.&lt;br /&gt;
* You should not be able to see column Activities. If you don't see this column then the test is successful.&lt;br /&gt;
&lt;br /&gt;
==== Issue#295 ====&lt;br /&gt;
===== How was this Issue Fixed? =====&lt;br /&gt;
When instructor clicks on delete button to delete courses/assignment, It gets deleted without confirming it. System should ask for confirmation whether to go ahead with deletion or not. We had to make following changes in _shared_action.html.erb&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
  &amp;lt;%= link_to image_tag('/assets/tree_view/delete-icon-24.png', :title =&amp;gt; 'Delete ' + model.downcase),&lt;br /&gt;
      { :controller =&amp;gt; controller, :action=&amp;gt;'delete', :id =&amp;gt; node.node_object_id , :data =&amp;gt; {:confirm =&amp;gt; 'Are you sure you want to delete?'}},&lt;br /&gt;
      { :title =&amp;gt; 'Delete ' + model.downcase } %&amp;gt;&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===== How to Test this fix? =====&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
1. https://github.com/expertiza/expertiza - Github link for original repository&lt;br /&gt;
&lt;br /&gt;
2. https://github.com/psabhyan/expertiza.git - Github Repository code for the updated code&lt;/div&gt;</summary>
		<author><name>Psabhyan</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2016/E1662._UI_issues/fixes&amp;diff=104138</id>
		<title>CSC/ECE 517 Fall 2016/E1662. UI issues/fixes</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2016/E1662._UI_issues/fixes&amp;diff=104138"/>
		<updated>2016-10-31T18:47:47Z</updated>

		<summary type="html">&lt;p&gt;Psabhyan: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= UI Issues/Fixes =&lt;br /&gt;
&lt;br /&gt;
=== Background ===&lt;br /&gt;
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:&lt;br /&gt;
* Faculty member adds students to a particular course. He also adds an assignment for the class.&lt;br /&gt;
* Assignment has a specific deadline, review period and final submission.&lt;br /&gt;
* Faculty members upload list of topics for the assignment.&lt;br /&gt;
* Students have to bid for the topic or they can suggest their own topic.&lt;br /&gt;
* At the end of the bidding process, students get a specific topic for the assignment.&lt;br /&gt;
* Students can form the teams by sending out invitations to other students.&lt;br /&gt;
* Students start working on the assignment and submit the assignment work before the initial submission date.&lt;br /&gt;
* Every student then gets to review work submitted by at least one team. Student submit their feedback in the review.&lt;br /&gt;
* Students then make the necessary changes as suggested by reviewer and submit the assignment before the final submission date.&lt;br /&gt;
* Students are graded on the basis of their work and reviews.&lt;br /&gt;
&lt;br /&gt;
=== Objective ===&lt;br /&gt;
The main objective this project is to fix the issues in the current system. The current system has following issues:&lt;br /&gt;
&lt;br /&gt;
* 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.&lt;br /&gt;
* If an assignment is completed, no one can sign up for topics or drop topics. Yet a completely blank &amp;quot;Actions&amp;quot; column on the signup sheet still appears. It would be better if the column did not appear.&lt;br /&gt;
* 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.&lt;br /&gt;
=== Issues ===&lt;br /&gt;
==== Issue#702 ====&lt;br /&gt;
===== How was this Issue Fixed? =====&lt;br /&gt;
Capturing Institution ID&lt;br /&gt;
&lt;br /&gt;
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. Following basic changes are required in order to fix this issue.&lt;br /&gt;
* Ensure that relationship exists between Course and Institution model classes.&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
# Establishing relationship between Course and Institution&lt;br /&gt;
class Institution &amp;lt; ActiveRecord::Base&lt;br /&gt;
  has_many :courses, dependent: :destroy&lt;br /&gt;
end&lt;br /&gt;
&lt;br /&gt;
class Course &amp;lt; ActiveRecord::Base&lt;br /&gt;
  belongs_to :institution, class_name: 'Institution', foreign_key: 'instituition_id'&lt;br /&gt;
end&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* Add a dropdown list in Course creation form so that user can select institution from the available options.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
&amp;lt;!--Adding a field so that user can select institution from the list--&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;&amp;lt;label for=&amp;quot;course_institutions_id&amp;quot;&amp;gt;Institution Name&amp;lt;/label&amp;gt;&amp;lt;br/&amp;gt;&lt;br /&gt;
  &amp;lt;%= select_tag :'institutions_id', options_from_collection_for_select(Institution.where.not(:name=&amp;gt;nil), 'id', 'name'), :include_blank =&amp;gt; &amp;quot;Please select...&amp;quot;,:required=&amp;gt;true %&amp;gt;&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* Ensure that the id for the selected institution is sent as a parameter along with other parameters back to controller.&lt;br /&gt;
* Once we receive all the data in controller Institution id should be saved in course table.&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
 @course = Course.new(name: params[:course][:name], directory_path: &lt;br /&gt;
params[:course][:directory_path], info: params[:course][:info], &lt;br /&gt;
institutions_id: params[:institutions_id], private: params[:course][:private])&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===== How to Test this fix? =====&lt;br /&gt;
* User should login to expertiza using Instructor's credentials.&lt;br /&gt;
* Go to Manage Courses&lt;br /&gt;
* Click on New Course button so as to open form for it.&lt;br /&gt;
* Fill up the form. you can see new field added as Institution Name. This is a drop down list which has list of Institutions.&lt;br /&gt;
* User has to select one of these institutions. If user tries to go ahead without selecting this then he will get an alert flash saying this is a required field.&lt;br /&gt;
* Once an institution is selected user can click on Create button to submit the form.&lt;br /&gt;
* Institution Id would be saved in database record against this particular entry of course in Course table. User can verify this by accessing Course table in the database. &lt;br /&gt;
==== Issue#316 ====&lt;br /&gt;
===== How was this Issue Fixed? =====&lt;br /&gt;
When student open sign up sheet for the Finished projects, he should not be able to take any actions for that assignment and hence Actions column should be hidden to him. For fixing this bug, we had to make following changes into sign_up_sheet/_table_line.html.erb.&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
&amp;lt;%if !@assignment.get_current_stage.eql?&amp;quot;Finished&amp;quot;%&amp;gt;&lt;br /&gt;
  &amp;lt;td align=&amp;quot;center&amp;quot;&amp;gt;&lt;br /&gt;
    &amp;lt;%= render :partial =&amp;gt; '/sign_up_sheet/actions', &lt;br /&gt;
    :locals =&amp;gt; {:i=&amp;gt;i,:topic=&amp;gt;topic, :is_suggested_topic=&amp;gt;is_suggested_topic ||= false} %&amp;gt;&lt;br /&gt;
  &amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;%end%&amp;gt;&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===== How to Test this fix? =====&lt;br /&gt;
* Login to expertiza using student credentials&lt;br /&gt;
* Go to assignment tab&lt;br /&gt;
* Look for the assignments which have current stage as &amp;quot;Finished&amp;quot;&lt;br /&gt;
* Open that assignment and check if &lt;br /&gt;
==== Issue#295 ====&lt;br /&gt;
===== How was this Issue Fixed? =====&lt;br /&gt;
When instructor clicks on delete button to delete courses/assignment, It gets deleted without confirming it. System should ask for confirmation whether to go ahead with deletion or not. We had to make following changes in _shared_action.html.erb&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
  &amp;lt;%= link_to image_tag('/assets/tree_view/delete-icon-24.png', :title =&amp;gt; 'Delete ' + model.downcase),&lt;br /&gt;
      { :controller =&amp;gt; controller, :action=&amp;gt;'delete', :id =&amp;gt; node.node_object_id , :data =&amp;gt; {:confirm =&amp;gt; 'Are you sure you want to delete?'}},&lt;br /&gt;
      { :title =&amp;gt; 'Delete ' + model.downcase } %&amp;gt;&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===== How to Test this fix? =====&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
1. https://github.com/expertiza/expertiza - Github link for original repository&lt;br /&gt;
&lt;br /&gt;
2. https://github.com/psabhyan/expertiza.git - Github Repository code for the updated code&lt;/div&gt;</summary>
		<author><name>Psabhyan</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2016/E1662._UI_issues/fixes&amp;diff=104044</id>
		<title>CSC/ECE 517 Fall 2016/E1662. UI issues/fixes</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2016/E1662._UI_issues/fixes&amp;diff=104044"/>
		<updated>2016-10-30T15:37:41Z</updated>

		<summary type="html">&lt;p&gt;Psabhyan: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= UI Issues/Fixes =&lt;br /&gt;
&lt;br /&gt;
=== Background ===&lt;br /&gt;
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:&lt;br /&gt;
* Faculty member adds students to a particular course. He also adds an assignment for the class.&lt;br /&gt;
* Assignment has a specific deadline, review period and final submission.&lt;br /&gt;
* Faculty members upload list of topics for the assignment.&lt;br /&gt;
* Students have to bid for the topic or they can suggest their own topic.&lt;br /&gt;
* At the end of the bidding process, students get a specific topic for the assignment.&lt;br /&gt;
* Students can form the teams by sending out invitations to other students.&lt;br /&gt;
* Students start working on the assignment and submit the assignment work before the initial submission date.&lt;br /&gt;
* Every student then gets to review work submitted by at least one team. Student submit their feedback in the review.&lt;br /&gt;
* Students then make the necessary changes as suggested by reviewer and submit the assignment before the final submission date.&lt;br /&gt;
* Students are graded on the basis of their work and reviews.&lt;br /&gt;
&lt;br /&gt;
=== Objective ===&lt;br /&gt;
The main objective this project is to fix the issues in the current system. The current system has following issues:&lt;br /&gt;
&lt;br /&gt;
* 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.&lt;br /&gt;
* If an assignment is completed, no one can sign up for topics or drop topics. Yet a completely blank &amp;quot;Actions&amp;quot; column on the signup sheet still appears. It would be better if the column did not appear.&lt;br /&gt;
* 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.&lt;br /&gt;
=== Issues ===&lt;br /&gt;
==== Issue#702 ====&lt;br /&gt;
===== How was this Issue Fixed =====&lt;br /&gt;
Capturing Institution ID&lt;br /&gt;
&lt;br /&gt;
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. Following basic changes are required in order to fix this issue.&lt;br /&gt;
* Ensure that relationship exists between Course and Institution model classes.&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
# Establishing relationship between Course and Institution&lt;br /&gt;
class Institution &amp;lt; ActiveRecord::Base&lt;br /&gt;
  has_many :courses, dependent: :destroy&lt;br /&gt;
end&lt;br /&gt;
&lt;br /&gt;
class Course &amp;lt; ActiveRecord::Base&lt;br /&gt;
  belongs_to :institution, class_name: 'Institution', foreign_key: 'instituition_id'&lt;br /&gt;
end&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* Add a dropdown list in Course creation form so that user can select institution from the available options.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
&amp;lt;!--Adding a field so that user can select institution from the list--&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;&amp;lt;label for=&amp;quot;course_institutions_id&amp;quot;&amp;gt;Institution Name&amp;lt;/label&amp;gt;&amp;lt;br/&amp;gt;&lt;br /&gt;
  &amp;lt;%= select_tag :'institutions_id', options_from_collection_for_select(Institution.where.not(:name=&amp;gt;nil), 'id', 'name'), :include_blank =&amp;gt; &amp;quot;Please select...&amp;quot;,:required=&amp;gt;true %&amp;gt;&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* Ensure that the id for the selected institution is sent as a parameter along with other parameters back to controller.&lt;br /&gt;
* Once we receive all the data in controller Institution id should be saved in course table.&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
 @course = Course.new(name: params[:course][:name], directory_path: &lt;br /&gt;
params[:course][:directory_path], info: params[:course][:info], &lt;br /&gt;
institutions_id: params[:institutions_id], private: params[:course][:private])&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===== How to Test this fix? =====&lt;br /&gt;
* User should login to expertiza using student credentials.&lt;br /&gt;
* Go to Manage Courses&lt;br /&gt;
* Click on New Course button so as to open form for it.&lt;br /&gt;
* Fill up the form. you can see new field added as Institution Name. This is a drop down list which has list of Institutions.&lt;br /&gt;
* User has to select one of these institutions. If user tries to go ahead without selecting this then he will get an alert flash saying this is a required field.&lt;br /&gt;
* Once an institution is selected user can click on Create button to submit the form.&lt;br /&gt;
* Institution Id would be saved in database record against this particular entry of course in Course table. User can verify this by accessing Course table in the database. &lt;br /&gt;
==== Issue#316 ====&lt;br /&gt;
When student open sign up sheet for the Finished projects, he should not be able to take any actions for that assignment and hence Actions column should be hidden to him. For fixing this bug, we had to make following changes into sign_up_sheet/_table_line.html.erb.&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
&amp;lt;%if !@assignment.get_current_stage.eql?&amp;quot;Finished&amp;quot;%&amp;gt;&lt;br /&gt;
  &amp;lt;td align=&amp;quot;center&amp;quot;&amp;gt;&lt;br /&gt;
    &amp;lt;%= render :partial =&amp;gt; '/sign_up_sheet/actions', &lt;br /&gt;
    :locals =&amp;gt; {:i=&amp;gt;i,:topic=&amp;gt;topic, :is_suggested_topic=&amp;gt;is_suggested_topic ||= false} %&amp;gt;&lt;br /&gt;
  &amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;%end%&amp;gt;&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Issue#295 ====&lt;br /&gt;
When instructor clicks on delete button to delete courses/assignment, It gets deleted without confirming it. System should ask for confirmation whether to go ahead with deletion or not. We had to make following changes in _shared_action.html.erb&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
  &amp;lt;%= link_to image_tag('/assets/tree_view/delete-icon-24.png', :title =&amp;gt; 'Delete ' + model.downcase),&lt;br /&gt;
      { :controller =&amp;gt; controller, :action=&amp;gt;'delete', :id =&amp;gt; node.node_object_id , :data =&amp;gt; {:confirm =&amp;gt; 'Are you sure you want to delete?'}},&lt;br /&gt;
      { :title =&amp;gt; 'Delete ' + model.downcase } %&amp;gt;&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
1. https://github.com/expertiza/expertiza - Github link for original repository&lt;br /&gt;
&lt;br /&gt;
2. https://github.com/psabhyan/expertiza.git - Github Repository code for the updated code&lt;/div&gt;</summary>
		<author><name>Psabhyan</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2016/E1662._UI_issues/fixes&amp;diff=104039</id>
		<title>CSC/ECE 517 Fall 2016/E1662. UI issues/fixes</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2016/E1662._UI_issues/fixes&amp;diff=104039"/>
		<updated>2016-10-30T15:27:56Z</updated>

		<summary type="html">&lt;p&gt;Psabhyan: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= UI Issues/Fixes =&lt;br /&gt;
&lt;br /&gt;
=== Background ===&lt;br /&gt;
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:&lt;br /&gt;
* Faculty member adds students to a particular course. He also adds an assignment for the class.&lt;br /&gt;
* Assignment has a specific deadline, review period and final submission.&lt;br /&gt;
* Faculty members upload list of topics for the assignment.&lt;br /&gt;
* Students have to bid for the topic or they can suggest their own topic.&lt;br /&gt;
* At the end of the bidding process, students get a specific topic for the assignment.&lt;br /&gt;
* Students can form the teams by sending out invitations to other students.&lt;br /&gt;
* Students start working on the assignment and submit the assignment work before the initial submission date.&lt;br /&gt;
* Every student then gets to review work submitted by at least one team. Student submit their feedback in the review.&lt;br /&gt;
* Students then make the necessary changes as suggested by reviewer and submit the assignment before the final submission date.&lt;br /&gt;
* Students are graded on the basis of their work and reviews.&lt;br /&gt;
&lt;br /&gt;
=== Objective ===&lt;br /&gt;
The main objective this project is to fix the issues in the current system. The current system has following issues:&lt;br /&gt;
&lt;br /&gt;
* 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.&lt;br /&gt;
* If an assignment is completed, no one can sign up for topics or drop topics. Yet a completely blank &amp;quot;Actions&amp;quot; column on the signup sheet still appears. It would be better if the column did not appear.&lt;br /&gt;
* 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.&lt;br /&gt;
=== Issues ===&lt;br /&gt;
==== Issue#702 ====&lt;br /&gt;
Capturing Institution ID&lt;br /&gt;
&lt;br /&gt;
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. Following basic changes are required in order to fix this issue.&lt;br /&gt;
* Ensure that relationship exists between Course and Institution model classes.&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
# Establishing relationship between Course and Institution&lt;br /&gt;
class Institution &amp;lt; ActiveRecord::Base&lt;br /&gt;
  has_many :courses, dependent: :destroy&lt;br /&gt;
end&lt;br /&gt;
&lt;br /&gt;
class Course &amp;lt; ActiveRecord::Base&lt;br /&gt;
  belongs_to :institution, class_name: 'Institution', foreign_key: 'instituition_id'&lt;br /&gt;
end&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* Add a dropdown list in Course creation form so that user can select institution from the available options.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
&amp;lt;!--Adding a field so that user can select institution from the list--&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;&amp;lt;label for=&amp;quot;course_institutions_id&amp;quot;&amp;gt;Institution Name&amp;lt;/label&amp;gt;&amp;lt;br/&amp;gt;&lt;br /&gt;
  &amp;lt;%= select_tag :'institutions_id', options_from_collection_for_select(Institution.where.not(:name=&amp;gt;nil), 'id', 'name'), :include_blank =&amp;gt; &amp;quot;Please select...&amp;quot;,:required=&amp;gt;true %&amp;gt;&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* Ensure that the id for the selected institution is sent as a parameter along with other parameters back to controller.&lt;br /&gt;
* Once we receive all the data in controller Institution id should be saved in course table.&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
 @course = Course.new(name: params[:course][:name], directory_path: &lt;br /&gt;
params[:course][:directory_path], info: params[:course][:info], &lt;br /&gt;
institutions_id: params[:institutions_id], private: params[:course][:private])&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Issue#316 ====&lt;br /&gt;
When student open sign up sheet for the Finished projects, he should not be able to take any actions for that assignment and hence Actions column should be hidden to him. For fixing this bug, we had to make following changes into sign_up_sheet/_table_line.html.erb.&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
&amp;lt;%if !@assignment.get_current_stage.eql?&amp;quot;Finished&amp;quot;%&amp;gt;&lt;br /&gt;
  &amp;lt;td align=&amp;quot;center&amp;quot;&amp;gt;&lt;br /&gt;
    &amp;lt;%= render :partial =&amp;gt; '/sign_up_sheet/actions', &lt;br /&gt;
    :locals =&amp;gt; {:i=&amp;gt;i,:topic=&amp;gt;topic, :is_suggested_topic=&amp;gt;is_suggested_topic ||= false} %&amp;gt;&lt;br /&gt;
  &amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;%end%&amp;gt;&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Issue#295 ====&lt;br /&gt;
When instructor clicks on delete button to delete courses/assignment, It gets deleted without confirming it. System should ask for confirmation whether to go ahead with deletion or not. We had to make following changes in _shared_action.html.erb&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
  &amp;lt;%= link_to image_tag('/assets/tree_view/delete-icon-24.png', :title =&amp;gt; 'Delete ' + model.downcase),&lt;br /&gt;
      { :controller =&amp;gt; controller, :action=&amp;gt;'delete', :id =&amp;gt; node.node_object_id , :data =&amp;gt; {:confirm =&amp;gt; 'Are you sure you want to delete?'}},&lt;br /&gt;
      { :title =&amp;gt; 'Delete ' + model.downcase } %&amp;gt;&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
1. https://github.com/expertiza/expertiza - Github link for original repository&lt;br /&gt;
&lt;br /&gt;
2. https://github.com/psabhyan/expertiza.git - Github Repository code for the updated code&lt;/div&gt;</summary>
		<author><name>Psabhyan</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2016/E1662._UI_issues/fixes&amp;diff=103604</id>
		<title>CSC/ECE 517 Fall 2016/E1662. UI issues/fixes</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2016/E1662._UI_issues/fixes&amp;diff=103604"/>
		<updated>2016-10-29T01:46:35Z</updated>

		<summary type="html">&lt;p&gt;Psabhyan: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= UI Issues/Fixes =&lt;br /&gt;
&lt;br /&gt;
=== Background ===&lt;br /&gt;
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:&lt;br /&gt;
* Faculty member adds students to a particular course. He also adds an assignment for the class.&lt;br /&gt;
* Assignment has a specific deadline, review period and final submission.&lt;br /&gt;
* Faculty members upload list of topics for the assignment.&lt;br /&gt;
* Students have to bid for the topic or they can suggest their own topic.&lt;br /&gt;
* At the end of the bidding process, students get a specific topic for the assignment.&lt;br /&gt;
* Students can form the teams by sending out invitations to other students.&lt;br /&gt;
* Students start working on the assignment and submit the assignment work before the initial submission date.&lt;br /&gt;
* Every student then gets to review work submitted by at least one team. Student submit their feedback in the review.&lt;br /&gt;
* Students then make the necessary changes as suggested by reviewer and submit the assignment before the final submission date.&lt;br /&gt;
* Students are graded on the basis of their work and reviews.&lt;br /&gt;
&lt;br /&gt;
=== Objective ===&lt;br /&gt;
The main objective this project is to fix the issues in the current system. The current system has following issues:&lt;br /&gt;
&lt;br /&gt;
* 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.&lt;br /&gt;
* If an assignment is completed, no one can sign up for topics or drop topics. Yet a completely blank &amp;quot;Actions&amp;quot; column on the signup sheet still appears. It would be better if the column did not appear.&lt;br /&gt;
* 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.&lt;br /&gt;
&lt;br /&gt;
=== Issue#702 ===&lt;br /&gt;
Capturing Institution ID&lt;br /&gt;
&lt;br /&gt;
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. Following basic changes are required in order to fix this issue.&lt;br /&gt;
* Ensure that relationship exists between Course and Institution model classes.&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
# Establishing relationship between Course and Institution&lt;br /&gt;
class Institution &amp;lt; ActiveRecord::Base&lt;br /&gt;
  has_many :courses, dependent: :destroy&lt;br /&gt;
end&lt;br /&gt;
&lt;br /&gt;
class Course &amp;lt; ActiveRecord::Base&lt;br /&gt;
  belongs_to :institution, class_name: 'Institution', foreign_key: 'instituition_id'&lt;br /&gt;
end&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* Add a dropdown list in Course creation form so that user can select institution from the available options.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
&amp;lt;!--Adding a field so that user can select institution from the list--&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;&amp;lt;label for=&amp;quot;course_institutions_id&amp;quot;&amp;gt;Institution Name&amp;lt;/label&amp;gt;&amp;lt;br/&amp;gt;&lt;br /&gt;
  &amp;lt;%= select_tag :'institutions_id', options_from_collection_for_select(Institution.where.not(:name=&amp;gt;nil), 'id', 'name'), :include_blank =&amp;gt; &amp;quot;Please select...&amp;quot;,:required=&amp;gt;true %&amp;gt;&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* Ensure that the id for the selected institution is sent as a parameter along with other parameters back to controller.&lt;br /&gt;
* Once we receive all the data in controller Institution id should be saved in course table.&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
 @course = Course.new(name: params[:course][:name], directory_path: &lt;br /&gt;
params[:course][:directory_path], info: params[:course][:info], &lt;br /&gt;
institutions_id: params[:institutions_id], private: params[:course][:private])&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Issue#316 ===&lt;br /&gt;
When student open sign up sheet for the Finished projects, he should not be able to take any actions for that assignment and hence Actions column should be hidden to him. For fixing this bug, we had to make following changes into sign_up_sheet/_table_line.html.erb.&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
&amp;lt;%if !@assignment.get_current_stage.eql?&amp;quot;Finished&amp;quot;%&amp;gt;&lt;br /&gt;
  &amp;lt;td align=&amp;quot;center&amp;quot;&amp;gt;&lt;br /&gt;
    &amp;lt;%= render :partial =&amp;gt; '/sign_up_sheet/actions', &lt;br /&gt;
    :locals =&amp;gt; {:i=&amp;gt;i,:topic=&amp;gt;topic, :is_suggested_topic=&amp;gt;is_suggested_topic ||= false} %&amp;gt;&lt;br /&gt;
  &amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;%end%&amp;gt;&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Issue#295 ===&lt;br /&gt;
When instructor clicks on delete button to delete courses/assignment, It gets deleted without confirming it. System should ask for confirmation whether to go ahead with deletion or not. We had to make following changes in _shared_action.html.erb&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
  &amp;lt;%= link_to image_tag('/assets/tree_view/delete-icon-24.png', :title =&amp;gt; 'Delete ' + model.downcase),&lt;br /&gt;
      { :controller =&amp;gt; controller, :action=&amp;gt;'delete', :id =&amp;gt; node.node_object_id , :data =&amp;gt; {:confirm =&amp;gt; 'Are you sure you want to delete?'}},&lt;br /&gt;
      { :title =&amp;gt; 'Delete ' + model.downcase } %&amp;gt;&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
1. https://github.com/expertiza/expertiza - Github link for original repository&lt;br /&gt;
&lt;br /&gt;
2. https://github.com/psabhyan/expertiza.git - Github Repository code for the updated code&lt;/div&gt;</summary>
		<author><name>Psabhyan</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2016/E1662._UI_issues/fixes&amp;diff=103579</id>
		<title>CSC/ECE 517 Fall 2016/E1662. UI issues/fixes</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2016/E1662._UI_issues/fixes&amp;diff=103579"/>
		<updated>2016-10-29T01:33:10Z</updated>

		<summary type="html">&lt;p&gt;Psabhyan: /* External Links */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= UI Issues/Fixes =&lt;br /&gt;
&lt;br /&gt;
=== Background ===&lt;br /&gt;
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:&lt;br /&gt;
* Faculty member adds students to a particular course. He also adds an assignment for the class.&lt;br /&gt;
* Assignment has a specific deadline, review period and final submission.&lt;br /&gt;
* Faculty members upload list of topics for the assignment.&lt;br /&gt;
* Students have to bid for the topic or they can suggest their own topic.&lt;br /&gt;
* At the end of the bidding process, students get a specific topic for the assignment.&lt;br /&gt;
* Students can form the teams by sending out invitations to other students.&lt;br /&gt;
* Students start working on the assignment and submit the assignment work before the initial submission date.&lt;br /&gt;
* Every student then gets to review work submitted by at least one team. Student submit their feedback in the review.&lt;br /&gt;
* Students then make the necessary changes as suggested by reviewer and submit the assignment before the final submission date.&lt;br /&gt;
* Students are graded on the basis of their work and reviews.&lt;br /&gt;
&lt;br /&gt;
=== Objective ===&lt;br /&gt;
The main objective this project is to fix the issues in the current system. The current system has following issues:&lt;br /&gt;
&lt;br /&gt;
* 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.&lt;br /&gt;
* If an assignment is completed, no one can sign up for topics or drop topics. Yet a completely blank &amp;quot;Actions&amp;quot; column on the signup sheet still appears. It would be better if the column did not appear.&lt;br /&gt;
* 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.&lt;br /&gt;
&lt;br /&gt;
=== Issue#702 ===&lt;br /&gt;
Capturing Institution ID&lt;br /&gt;
&lt;br /&gt;
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. Following basic changes are required in order to fix this issue.&lt;br /&gt;
* Ensure that relationship exists between Course and Institution model classes.&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
# Establishing relationship between Course and Institution&lt;br /&gt;
class Institution &amp;lt; ActiveRecord::Base&lt;br /&gt;
  has_many :courses, dependent: :destroy&lt;br /&gt;
end&lt;br /&gt;
&lt;br /&gt;
class Course &amp;lt; ActiveRecord::Base&lt;br /&gt;
  belongs_to :institution, class_name: 'Institution', foreign_key: 'instituition_id'&lt;br /&gt;
end&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* Add a dropdown list in Course creation form so that user can select institution from the available options.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
&amp;lt;!--Adding a field so that user can select institution from the list--&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;&amp;lt;label for=&amp;quot;course_institutions_id&amp;quot;&amp;gt;Institution Name&amp;lt;/label&amp;gt;&amp;lt;br/&amp;gt;&lt;br /&gt;
  &amp;lt;%= select_tag :'institutions_id', options_from_collection_for_select(Institution.where.not(:name=&amp;gt;nil), 'id', 'name'), :include_blank =&amp;gt; &amp;quot;Please select...&amp;quot;,:required=&amp;gt;true %&amp;gt;&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* Ensure that the id for the selected institution is sent as a parameter along with other parameters back to controller.&lt;br /&gt;
* Once we receive all the data in controller Institution id should be saved in course table.&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
 @course = Course.new(name: params[:course][:name], directory_path: &lt;br /&gt;
params[:course][:directory_path], info: params[:course][:info], &lt;br /&gt;
institutions_id: params[:institutions_id], private: params[:course][:private])&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Issue#316 ===&lt;br /&gt;
When student open sign up sheet for the Finished projects, he should not be able to take any actions for that assignment and hence Actions column should be hidden to him. For fixing this bug, we had to make following changes into sign_up_sheet/_table_line.html.erb.&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
&amp;lt;%if !@assignment.get_current_stage.eql?&amp;quot;Finished&amp;quot;%&amp;gt;&lt;br /&gt;
  &amp;lt;td align=&amp;quot;center&amp;quot;&amp;gt;&lt;br /&gt;
    &amp;lt;%= render :partial =&amp;gt; '/sign_up_sheet/actions', &lt;br /&gt;
    :locals =&amp;gt; {:i=&amp;gt;i,:topic=&amp;gt;topic, :is_suggested_topic=&amp;gt;is_suggested_topic ||= false} %&amp;gt;&lt;br /&gt;
  &amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;%end%&amp;gt;&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
1. https://github.com/expertiza/expertiza - Github link for original repository&lt;br /&gt;
&lt;br /&gt;
2. https://github.com/psabhyan/expertiza.git - Github Repository code for the updated code&lt;/div&gt;</summary>
		<author><name>Psabhyan</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2016/E1671._Unit_Tests_for_participants.rb_Hierarchy&amp;diff=103577</id>
		<title>CSC/ECE 517 Fall 2016/E1671. Unit Tests for participants.rb Hierarchy</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2016/E1671._Unit_Tests_for_participants.rb_Hierarchy&amp;diff=103577"/>
		<updated>2016-10-29T01:32:33Z</updated>

		<summary type="html">&lt;p&gt;Psabhyan: /* References */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This wiki page is for the description of changes made under E1671 OSS assignment for Fall 2016, CSC/ECE 517.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Background ==&lt;br /&gt;
Expertiza is an open source web based peer review system developed and maintained by students and faculty members at North Carolina State University. It enables students enrolled in a particular course to form online teams and complete assignments.&lt;br /&gt;
&lt;br /&gt;
== Problem ==&lt;br /&gt;
The participant, course_participant and assignment_pariticipant models does not have any unit tests.&lt;br /&gt;
&lt;br /&gt;
== What to do ==&lt;br /&gt;
*Create a Fatcory for assignment participant and course participant model.&lt;br /&gt;
&lt;br /&gt;
*Test the relationships and validations&lt;br /&gt;
&lt;br /&gt;
*Write model spec for major instances&lt;br /&gt;
&lt;br /&gt;
== Run the test ==&lt;br /&gt;
&lt;br /&gt;
The tests can be run on the terminal using following commands:&lt;br /&gt;
&lt;br /&gt;
For participant:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
 rspec spec/models/participant_spec.rb&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
For assignment_participant:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
 rspec spec/models/assignment_participant_spec.rb&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
For participant:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
 rspec spec/models/assignment_participant_spec.rb&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Unit test ==&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
1. https://github.com/expertiza/expertiza - Github link for original repository&lt;br /&gt;
&lt;br /&gt;
2. https://en.wikipedia.org/wiki/RSpec - RSpec Tutorial on Wiki&lt;br /&gt;
&lt;br /&gt;
3. https://github.com/jnicklas/capybara Capybara Documentation on Github&lt;/div&gt;</summary>
		<author><name>Psabhyan</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2016/E1671._Unit_Tests_for_participants.rb_Hierarchy&amp;diff=103569</id>
		<title>CSC/ECE 517 Fall 2016/E1671. Unit Tests for participants.rb Hierarchy</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2016/E1671._Unit_Tests_for_participants.rb_Hierarchy&amp;diff=103569"/>
		<updated>2016-10-29T01:27:10Z</updated>

		<summary type="html">&lt;p&gt;Psabhyan: /* References */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This wiki page is for the description of changes made under E1671 OSS assignment for Fall 2016, CSC/ECE 517.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Background ==&lt;br /&gt;
Expertiza is an open source web based peer review system developed and maintained by students and faculty members at North Carolina State University. It enables students enrolled in a particular course to form online teams and complete assignments.&lt;br /&gt;
&lt;br /&gt;
== Problem ==&lt;br /&gt;
The participant, course_participant and assignment_pariticipant models does not have any unit tests.&lt;br /&gt;
&lt;br /&gt;
== What to do ==&lt;br /&gt;
*Create a Fatcory for assignment participant and course participant model.&lt;br /&gt;
&lt;br /&gt;
*Test the relationships and validations&lt;br /&gt;
&lt;br /&gt;
*Write model spec for major instances&lt;br /&gt;
&lt;br /&gt;
== Run the test ==&lt;br /&gt;
&lt;br /&gt;
The tests can be run on the terminal using following commands:&lt;br /&gt;
&lt;br /&gt;
For participant:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
 rspec spec/models/participant_spec.rb&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
For assignment_participant:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
 rspec spec/models/assignment_participant_spec.rb&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
For participant:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
 rspec spec/models/assignment_participant_spec.rb&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Unit test ==&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
1. https://github.com/expertiza/expertiza - Github link for original repository&lt;br /&gt;
&lt;br /&gt;
2. https://github.com/psabhyan/expertiza.git - Github Repository code for the updated code&lt;/div&gt;</summary>
		<author><name>Psabhyan</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2016/E1662._UI_issues/fixes&amp;diff=103560</id>
		<title>CSC/ECE 517 Fall 2016/E1662. UI issues/fixes</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2016/E1662._UI_issues/fixes&amp;diff=103560"/>
		<updated>2016-10-29T01:23:40Z</updated>

		<summary type="html">&lt;p&gt;Psabhyan: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= UI Issues/Fixes =&lt;br /&gt;
&lt;br /&gt;
=== Background ===&lt;br /&gt;
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:&lt;br /&gt;
* Faculty member adds students to a particular course. He also adds an assignment for the class.&lt;br /&gt;
* Assignment has a specific deadline, review period and final submission.&lt;br /&gt;
* Faculty members upload list of topics for the assignment.&lt;br /&gt;
* Students have to bid for the topic or they can suggest their own topic.&lt;br /&gt;
* At the end of the bidding process, students get a specific topic for the assignment.&lt;br /&gt;
* Students can form the teams by sending out invitations to other students.&lt;br /&gt;
* Students start working on the assignment and submit the assignment work before the initial submission date.&lt;br /&gt;
* Every student then gets to review work submitted by at least one team. Student submit their feedback in the review.&lt;br /&gt;
* Students then make the necessary changes as suggested by reviewer and submit the assignment before the final submission date.&lt;br /&gt;
* Students are graded on the basis of their work and reviews.&lt;br /&gt;
&lt;br /&gt;
=== Objective ===&lt;br /&gt;
The main objective this project is to fix the issues in the current system. The current system has following issues:&lt;br /&gt;
&lt;br /&gt;
* 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.&lt;br /&gt;
* If an assignment is completed, no one can sign up for topics or drop topics. Yet a completely blank &amp;quot;Actions&amp;quot; column on the signup sheet still appears. It would be better if the column did not appear.&lt;br /&gt;
* 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.&lt;br /&gt;
&lt;br /&gt;
=== Issue#702 ===&lt;br /&gt;
Capturing Institution ID&lt;br /&gt;
&lt;br /&gt;
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. Following basic changes are required in order to fix this issue.&lt;br /&gt;
* Ensure that relationship exists between Course and Institution model classes.&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
# Establishing relationship between Course and Institution&lt;br /&gt;
class Institution &amp;lt; ActiveRecord::Base&lt;br /&gt;
  has_many :courses, dependent: :destroy&lt;br /&gt;
end&lt;br /&gt;
&lt;br /&gt;
class Course &amp;lt; ActiveRecord::Base&lt;br /&gt;
  belongs_to :institution, class_name: 'Institution', foreign_key: 'instituition_id'&lt;br /&gt;
end&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* Add a dropdown list in Course creation form so that user can select institution from the available options.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
&amp;lt;!--Adding a field so that user can select institution from the list--&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;&amp;lt;label for=&amp;quot;course_institutions_id&amp;quot;&amp;gt;Institution Name&amp;lt;/label&amp;gt;&amp;lt;br/&amp;gt;&lt;br /&gt;
  &amp;lt;%= select_tag :'institutions_id', options_from_collection_for_select(Institution.where.not(:name=&amp;gt;nil), 'id', 'name'), :include_blank =&amp;gt; &amp;quot;Please select...&amp;quot;,:required=&amp;gt;true %&amp;gt;&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* Ensure that the id for the selected institution is sent as a parameter along with other parameters back to controller.&lt;br /&gt;
* Once we receive all the data in controller Institution id should be saved in course table.&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
 @course = Course.new(name: params[:course][:name], directory_path: &lt;br /&gt;
params[:course][:directory_path], info: params[:course][:info], &lt;br /&gt;
institutions_id: params[:institutions_id], private: params[:course][:private])&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Issue#316 ===&lt;br /&gt;
When student open sign up sheet for the Finished projects, he should not be able to take any actions for that assignment and hence Actions column should be hidden to him. For fixing this bug, we had to make following changes into sign_up_sheet/_table_line.html.erb.&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
&amp;lt;%if !@assignment.get_current_stage.eql?&amp;quot;Finished&amp;quot;%&amp;gt;&lt;br /&gt;
  &amp;lt;td align=&amp;quot;center&amp;quot;&amp;gt;&lt;br /&gt;
    &amp;lt;%= render :partial =&amp;gt; '/sign_up_sheet/actions', &lt;br /&gt;
    :locals =&amp;gt; {:i=&amp;gt;i,:topic=&amp;gt;topic, :is_suggested_topic=&amp;gt;is_suggested_topic ||= false} %&amp;gt;&lt;br /&gt;
  &amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;%end%&amp;gt;&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== External Links ===&lt;br /&gt;
# link for forked repository&lt;br /&gt;
# Github link for original repository&lt;br /&gt;
# Github link for Capybara&lt;/div&gt;</summary>
		<author><name>Psabhyan</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2016/E1662._UI_issues/fixes&amp;diff=103485</id>
		<title>CSC/ECE 517 Fall 2016/E1662. UI issues/fixes</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2016/E1662._UI_issues/fixes&amp;diff=103485"/>
		<updated>2016-10-29T00:55:24Z</updated>

		<summary type="html">&lt;p&gt;Psabhyan: /* Issue#702 */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= UI Issues/Fixes =&lt;br /&gt;
&lt;br /&gt;
=== Background ===&lt;br /&gt;
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:&lt;br /&gt;
* Faculty member adds students to a particular course. He also adds an assignment for the class.&lt;br /&gt;
* Assignment has a specific deadline, review period and final submission.&lt;br /&gt;
* Faculty members upload list of topics for the assignment.&lt;br /&gt;
* Students have to bid for the topic or they can suggest their own topic.&lt;br /&gt;
* At the end of the bidding process, students get a specific topic for the assignment.&lt;br /&gt;
* Students can form the teams by sending out invitations to other students.&lt;br /&gt;
* Students start working on the assignment and submit the assignment work before the initial submission date.&lt;br /&gt;
* Every student then gets to review work submitted by at least one team. Student submit their feedback in the review.&lt;br /&gt;
* Students then make the necessary changes as suggested by reviewer and submit the assignment before the final submission date.&lt;br /&gt;
* Students are graded on the basis of their work and reviews.&lt;br /&gt;
&lt;br /&gt;
=== Objective ===&lt;br /&gt;
The main objective this project is to fix the issues in the current system. The current system has following issues:&lt;br /&gt;
&lt;br /&gt;
* 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.&lt;br /&gt;
* If an assignment is completed, no one can sign up for topics or drop topics. Yet a completely blank &amp;quot;Actions&amp;quot; column on the signup sheet still appears. It would be better if the column did not appear.&lt;br /&gt;
* 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.&lt;br /&gt;
&lt;br /&gt;
=== Issue#702 ===&lt;br /&gt;
Capturing Institution ID&lt;br /&gt;
&lt;br /&gt;
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. Following basic changes are required in order to fix this issue.&lt;br /&gt;
* Ensure that relationship exists between Course and Institution model classes.&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
# Establishing relationship between Course and Institution&lt;br /&gt;
class Institution &amp;lt; ActiveRecord::Base&lt;br /&gt;
  has_many :courses, dependent: :destroy&lt;br /&gt;
end&lt;br /&gt;
&lt;br /&gt;
class Course &amp;lt; ActiveRecord::Base&lt;br /&gt;
  belongs_to :institution, class_name: 'Institution', foreign_key: 'instituition_id'&lt;br /&gt;
end&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* Add a dropdown list in Course creation form so that user can select institution from the available options.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
&amp;lt;!--Adding a field so that user can select institution from the list--&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;&amp;lt;label for=&amp;quot;course_institutions_id&amp;quot;&amp;gt;Institution Name&amp;lt;/label&amp;gt;&amp;lt;br/&amp;gt;&lt;br /&gt;
  &amp;lt;%= select_tag :'institutions_id', options_from_collection_for_select(Institution.where.not(:name=&amp;gt;nil), 'id', 'name'), :include_blank =&amp;gt; &amp;quot;Please select...&amp;quot;,:required=&amp;gt;true %&amp;gt;&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* Ensure that the id for the selected institution is sent as a parameter along with other parameters back to controller.&lt;br /&gt;
* Once we receive all the data in controller Institution id should be saved in course table.&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
 @course = Course.new(name: params[:course][:name], directory_path: &lt;br /&gt;
params[:course][:directory_path], info: params[:course][:info], &lt;br /&gt;
institutions_id: params[:institutions_id], private: params[:course][:private])&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Functional Tests Implementation ===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Running the tests ===&lt;br /&gt;
&lt;br /&gt;
The tests can be run on the terminal using the command:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
 rspec specfile.rb&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Whether the test fails or succeeds, allows us to determine which parts of the system are functioning properly.&lt;br /&gt;
&lt;br /&gt;
=== External Links ===&lt;br /&gt;
# link for forked repository&lt;br /&gt;
# Github link for original repository&lt;br /&gt;
# Github link for Capybara&lt;/div&gt;</summary>
		<author><name>Psabhyan</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2016/E1662._UI_issues/fixes&amp;diff=103483</id>
		<title>CSC/ECE 517 Fall 2016/E1662. UI issues/fixes</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2016/E1662._UI_issues/fixes&amp;diff=103483"/>
		<updated>2016-10-29T00:54:30Z</updated>

		<summary type="html">&lt;p&gt;Psabhyan: /* Issue#702 */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= UI Issues/Fixes =&lt;br /&gt;
&lt;br /&gt;
=== Background ===&lt;br /&gt;
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:&lt;br /&gt;
* Faculty member adds students to a particular course. He also adds an assignment for the class.&lt;br /&gt;
* Assignment has a specific deadline, review period and final submission.&lt;br /&gt;
* Faculty members upload list of topics for the assignment.&lt;br /&gt;
* Students have to bid for the topic or they can suggest their own topic.&lt;br /&gt;
* At the end of the bidding process, students get a specific topic for the assignment.&lt;br /&gt;
* Students can form the teams by sending out invitations to other students.&lt;br /&gt;
* Students start working on the assignment and submit the assignment work before the initial submission date.&lt;br /&gt;
* Every student then gets to review work submitted by at least one team. Student submit their feedback in the review.&lt;br /&gt;
* Students then make the necessary changes as suggested by reviewer and submit the assignment before the final submission date.&lt;br /&gt;
* Students are graded on the basis of their work and reviews.&lt;br /&gt;
&lt;br /&gt;
=== Objective ===&lt;br /&gt;
The main objective this project is to fix the issues in the current system. The current system has following issues:&lt;br /&gt;
&lt;br /&gt;
* 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.&lt;br /&gt;
* If an assignment is completed, no one can sign up for topics or drop topics. Yet a completely blank &amp;quot;Actions&amp;quot; column on the signup sheet still appears. It would be better if the column did not appear.&lt;br /&gt;
* 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.&lt;br /&gt;
&lt;br /&gt;
=== Issue#702 ===&lt;br /&gt;
Capturing Institution ID&lt;br /&gt;
&lt;br /&gt;
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. Following basic changes are required in order to fix this issue.&lt;br /&gt;
* Ensure that relationship exists between Course and Institution model classes.&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
# Establishing relationship between Course and Institution&lt;br /&gt;
class Institution &amp;lt; ActiveRecord::Base&lt;br /&gt;
  has_many :courses, dependent: :destroy&lt;br /&gt;
end&lt;br /&gt;
&lt;br /&gt;
class Course &amp;lt; ActiveRecord::Base&lt;br /&gt;
  belongs_to :institution, class_name: 'Institution', foreign_key: 'instituition_id'&lt;br /&gt;
end&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* Add a dropdown list in Course creation form so that user can select institution from the available options.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
&amp;lt;!--Adding a field so that user can select institution from the list--&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;&amp;lt;label for=&amp;quot;course_institutions_id&amp;quot;&amp;gt;Institution Name&amp;lt;/label&amp;gt;&amp;lt;br/&amp;gt;&lt;br /&gt;
  &amp;lt;%= select_tag :'institutions_id', options_from_collection_for_select(Institution.where.not(:name=&amp;gt;nil), 'id', 'name'), :include_blank =&amp;gt; &amp;quot;Please select...&amp;quot;,:required=&amp;gt;true %&amp;gt;&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* Ensure that the id for the selected institution is sent as a parameter along with other parameters back to controller.&lt;br /&gt;
* Once we receive all the data in controller Institution id should be saved in course table.&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
 @course = Course.new(name: params[:course][:name], directory_path: params[:course][:directory_path], info: params[:course][:info], institutions_id: params[:institutions_id], private: params[:course][:private])&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Functional Tests Implementation ===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Running the tests ===&lt;br /&gt;
&lt;br /&gt;
The tests can be run on the terminal using the command:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
 rspec specfile.rb&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Whether the test fails or succeeds, allows us to determine which parts of the system are functioning properly.&lt;br /&gt;
&lt;br /&gt;
=== External Links ===&lt;br /&gt;
# link for forked repository&lt;br /&gt;
# Github link for original repository&lt;br /&gt;
# Github link for Capybara&lt;/div&gt;</summary>
		<author><name>Psabhyan</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2016/E1662._UI_issues/fixes&amp;diff=103452</id>
		<title>CSC/ECE 517 Fall 2016/E1662. UI issues/fixes</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2016/E1662._UI_issues/fixes&amp;diff=103452"/>
		<updated>2016-10-29T00:39:44Z</updated>

		<summary type="html">&lt;p&gt;Psabhyan: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= UI Issues/Fixes =&lt;br /&gt;
&lt;br /&gt;
=== Background ===&lt;br /&gt;
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:&lt;br /&gt;
* Faculty member adds students to a particular course. He also adds an assignment for the class.&lt;br /&gt;
* Assignment has a specific deadline, review period and final submission.&lt;br /&gt;
* Faculty members upload list of topics for the assignment.&lt;br /&gt;
* Students have to bid for the topic or they can suggest their own topic.&lt;br /&gt;
* At the end of the bidding process, students get a specific topic for the assignment.&lt;br /&gt;
* Students can form the teams by sending out invitations to other students.&lt;br /&gt;
* Students start working on the assignment and submit the assignment work before the initial submission date.&lt;br /&gt;
* Every student then gets to review work submitted by at least one team. Student submit their feedback in the review.&lt;br /&gt;
* Students then make the necessary changes as suggested by reviewer and submit the assignment before the final submission date.&lt;br /&gt;
* Students are graded on the basis of their work and reviews.&lt;br /&gt;
&lt;br /&gt;
=== Objective ===&lt;br /&gt;
The main objective this project is to fix the issues in the current system. The current system has following issues:&lt;br /&gt;
&lt;br /&gt;
* 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.&lt;br /&gt;
* If an assignment is completed, no one can sign up for topics or drop topics. Yet a completely blank &amp;quot;Actions&amp;quot; column on the signup sheet still appears. It would be better if the column did not appear.&lt;br /&gt;
* 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.&lt;br /&gt;
&lt;br /&gt;
=== Issue#702 ===&lt;br /&gt;
Capturing Institution ID&lt;br /&gt;
&lt;br /&gt;
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. Following basic changes are required in order to fix this issue.&lt;br /&gt;
* Ensure that relationship exists between Course and Institution model classes.&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;&amp;lt;label for=&amp;quot;course_institutions_id&amp;quot;&amp;gt;Institution Name&amp;lt;/label&amp;gt;&amp;lt;br/&amp;gt;&lt;br /&gt;
  &amp;lt;%= select_tag :'institutions_id', options_from_collection_for_select(Institution.where.not(:name=&amp;gt;nil), 'id', 'name'), :include_blank =&amp;gt; &amp;quot;Please select...&amp;quot;,:required=&amp;gt;true %&amp;gt;&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* Add a dropdown list in Course creation form so that user can select institution from the available options.&lt;br /&gt;
* Ensure that the id for the selected institution is sent as a parameter along with other parameters back to controller.&lt;br /&gt;
* Once we receive all the data in controller Institution id should be saved in course table.&lt;br /&gt;
 &lt;br /&gt;
=== Functional Tests Implementation ===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Running the tests ===&lt;br /&gt;
&lt;br /&gt;
The tests can be run on the terminal using the command:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
 rspec specfile.rb&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Whether the test fails or succeeds, allows us to determine which parts of the system are functioning properly.&lt;br /&gt;
&lt;br /&gt;
=== External Links ===&lt;br /&gt;
# link for forked repository&lt;br /&gt;
# Github link for original repository&lt;br /&gt;
# Github link for Capybara&lt;/div&gt;</summary>
		<author><name>Psabhyan</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2016/E1662._UI_issues/fixes&amp;diff=103383</id>
		<title>CSC/ECE 517 Fall 2016/E1662. UI issues/fixes</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2016/E1662._UI_issues/fixes&amp;diff=103383"/>
		<updated>2016-10-29T00:06:01Z</updated>

		<summary type="html">&lt;p&gt;Psabhyan: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= UI Issues/Fixes =&lt;br /&gt;
&lt;br /&gt;
=== Background ===&lt;br /&gt;
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:&lt;br /&gt;
* Faculty member adds students to a particular course. He also adds an assignment for the class.&lt;br /&gt;
* Assignment has a specific deadline, review period and final submission.&lt;br /&gt;
* Faculty members upload list of topics for the assignment.&lt;br /&gt;
* Students have to bid for the topic or they can suggest their own topic.&lt;br /&gt;
* At the end of the bidding process, students get a specific topic for the assignment.&lt;br /&gt;
* Students can form the teams by sending out invitations to other students.&lt;br /&gt;
* Students start working on the assignment and submit the assignment work before the initial submission date.&lt;br /&gt;
* Every student then gets to review work submitted by at least one team. Student submit their feedback in the review.&lt;br /&gt;
* Students then make the necessary changes as suggested by reviewer and submit the assignment before the final submission date.&lt;br /&gt;
* Students are graded on the basis of their work and reviews.&lt;br /&gt;
&lt;br /&gt;
=== Objective ===&lt;br /&gt;
The main objective this project is to fix the issues in the current system. The current system has following issues:&lt;br /&gt;
&lt;br /&gt;
* 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.&lt;br /&gt;
* If an assignment is completed, no one can sign up for topics or drop topics. Yet a completely blank &amp;quot;Actions&amp;quot; column on the signup sheet still appears. It would be better if the column did not appear.&lt;br /&gt;
* 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.&lt;br /&gt;
&lt;br /&gt;
=== Issue#702 ===&lt;br /&gt;
Capturing Institution ID&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
 &lt;br /&gt;
=== Functional Tests Implementation ===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Running the tests ===&lt;br /&gt;
&lt;br /&gt;
The tests can be run on the terminal using the command:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
 rspec specfile.rb&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Whether the test fails or succeeds, allows us to determine which parts of the system are functioning properly.&lt;br /&gt;
&lt;br /&gt;
=== External Links ===&lt;br /&gt;
# link for forked repository&lt;br /&gt;
# Github link for original repository&lt;br /&gt;
# Github link for Capybara&lt;/div&gt;</summary>
		<author><name>Psabhyan</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2016/E1662._UI_issues/fixes&amp;diff=103344</id>
		<title>CSC/ECE 517 Fall 2016/E1662. UI issues/fixes</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2016/E1662._UI_issues/fixes&amp;diff=103344"/>
		<updated>2016-10-28T23:52:43Z</updated>

		<summary type="html">&lt;p&gt;Psabhyan: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= UI Issues/Fixes =&lt;br /&gt;
&lt;br /&gt;
=== Background ===&lt;br /&gt;
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:&lt;br /&gt;
* Faculty member adds students to a particular course. He also adds an assignment for the class.&lt;br /&gt;
* Assignment has a specific deadline, review period and final submission.&lt;br /&gt;
* Faculty members upload list of topics for the assignment.&lt;br /&gt;
* Students have to bid for the topic or they can suggest their own topic.&lt;br /&gt;
* At the end of the bidding process, students get a specific topic for the assignment.&lt;br /&gt;
* Students can form the teams by sending out invitations to other students.&lt;br /&gt;
* Students start working on the assignment and submit the assignment work before the initial submission date.&lt;br /&gt;
* Every student then gets to review work submitted by at least one team. Student submit their feedback in the review.&lt;br /&gt;
* Students then make the necessary changes as suggested by reviewer and submit the assignment before the final submission date.&lt;br /&gt;
* Students are graded on the basis of their work and reviews.&lt;br /&gt;
&lt;br /&gt;
=== Objective ===&lt;br /&gt;
The main objective this project is to fix the issues in the current system. The current system has following issues:&lt;br /&gt;
&lt;br /&gt;
* 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.&lt;br /&gt;
* If an assignment is completed, no one can sign up for topics or drop topics. Yet a completely blank &amp;quot;Actions&amp;quot; column on the signup sheet still appears. It would be better if the column did not appear.&lt;br /&gt;
* 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.&lt;br /&gt;
&lt;br /&gt;
=== Issue Details ===&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
Capybara gem allows a user to test their web application through simulations.&lt;br /&gt;
&lt;br /&gt;
=== Functional Tests Implementation ===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Running the tests ===&lt;br /&gt;
&lt;br /&gt;
The tests can be run on the terminal using the command:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
 rspec specfile.rb&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Whether the test fails or succeeds, allows us to determine which parts of the system are functioning properly.&lt;br /&gt;
&lt;br /&gt;
=== External Links ===&lt;br /&gt;
# link for forked repository&lt;br /&gt;
# Github link for original repository&lt;br /&gt;
# Github link for Capybara&lt;/div&gt;</summary>
		<author><name>Psabhyan</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2016/E1662._UI_issues/fixes&amp;diff=103307</id>
		<title>CSC/ECE 517 Fall 2016/E1662. UI issues/fixes</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2016/E1662._UI_issues/fixes&amp;diff=103307"/>
		<updated>2016-10-28T23:35:19Z</updated>

		<summary type="html">&lt;p&gt;Psabhyan: Created page with &amp;quot;= 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 b...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= UI Issues/Fixes =&lt;br /&gt;
&lt;br /&gt;
=== Background ===&lt;br /&gt;
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:&lt;br /&gt;
* Faculty member adds students to a particular course. He also adds an assignment for the class.&lt;br /&gt;
* Assignment has a specific deadline, review period and final submission.&lt;br /&gt;
* Faculty members upload list of topics for the assignment.&lt;br /&gt;
* Students have to bid for the topic or they can suggest their own topic.&lt;br /&gt;
* At the end of the bidding process, students get a specific topic for the assignment.&lt;br /&gt;
* Students can form the teams by sending out invitations to other students.&lt;br /&gt;
* Students start working on the assignment and submit the assignment work before the initial submission date.&lt;br /&gt;
* Every student then gets to review work submitted by at least one team. Student submit their feedback in the review.&lt;br /&gt;
* Students then make the necessary changes as suggested by reviewer and submit the assignment before the final submission date.&lt;br /&gt;
* Students are graded on the basis of their work and reviews.&lt;br /&gt;
&lt;br /&gt;
=== Purpose ===&lt;br /&gt;
The purpose of this task is to write functional tests for team functionality. Once an assignment is out, a student can select this assignment and others can join in the team. To test this functionality we wrote functional tests for the various scenarios.&lt;br /&gt;
One such scenario is :&lt;br /&gt;
&lt;br /&gt;
* Once the assignment is out and a student selects it, he/she can send out invites to other students to join the team.&lt;br /&gt;
* Invited students can accept the invitation and join the team.&lt;br /&gt;
&lt;br /&gt;
=== Functional Tests ===&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
Capybara gem allows a user to test their web application through simulations.&lt;br /&gt;
&lt;br /&gt;
=== Functional Tests Implementation ===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Running the tests ===&lt;br /&gt;
&lt;br /&gt;
The tests can be run on the terminal using the command:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
 rspec specfile.rb&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Whether the test fails or succeeds, allows us to determine which parts of the system are functioning properly.&lt;br /&gt;
&lt;br /&gt;
=== External Links ===&lt;br /&gt;
# link for forked repository&lt;br /&gt;
# Github link for original repository&lt;br /&gt;
# Github link for Capybara&lt;/div&gt;</summary>
		<author><name>Psabhyan</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2016&amp;diff=102827</id>
		<title>CSC/ECE 517 Fall 2016</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2016&amp;diff=102827"/>
		<updated>2016-10-28T19:09:25Z</updated>

		<summary type="html">&lt;p&gt;Psabhyan: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[http://www.example.com link title]==Calibration Assignment Submissions==&lt;br /&gt;
*[[Calibration Assignment Submission (Firebrick JS)]]&lt;br /&gt;
*[[Calibration Assignment Submission (Active Job)]]&lt;br /&gt;
==Writing Assignments 2==&lt;br /&gt;
*[[CSC/ECE 517 Fall 2016/E1666. Test team functionality]]&lt;br /&gt;
*[[CSC/ECE 517 Fall 2016/E1643. Refactor Suggestion controller]]&lt;br /&gt;
*[[CSC/ECE 517 Fall 2016/E1631. Refactoring Bidding Interface]]&lt;br /&gt;
*[[CSC/ECE 517 Fall 2016/E1674.Refactor leaderboard.rb and write unit tests]]&lt;br /&gt;
*[[CSC/ECE 517 Fall 2016/E1668.Test e-mailing functionality]]&lt;br /&gt;
*[[CSC/ECE 517 Fall 2016/E1658. Refractor lottery_controller.rb and write integration tests]]&lt;br /&gt;
*[[CSC/ECE 517 Fall 2016/E1660. Review requirements and thresholds]]&lt;br /&gt;
*[[CSC/ECE 517 Fall 2016/E1650. Sort instructor views alphabetically by default]]&lt;br /&gt;
*[[CSC/ECE 517 Fall 2016/E1644. Refactor and test Teams Controller]]&lt;br /&gt;
*[[CSC/ECE 517 Fall 2016/E1659. Refactor on_the_fly_calc.rb]]&lt;br /&gt;
*[[CSC/ECE 517 Fall 2016/E1657. Introduce a Student View for instructors]]&lt;br /&gt;
*[[CSC/ECE 517 Fall 2016/E1653. Fix and improve rubric criteria]]&lt;br /&gt;
*[[CSC/ECE 517 Fall 2016/E1642. Refactor review_response_map.rb]]&lt;br /&gt;
*[[CSC/ECE 517 Fall 2016/E1666. Test team functionality]]&lt;br /&gt;
*[[CSC/ECE_517_Fall_2016/E1654. Improve_date-picker_and_deadlines]]&lt;br /&gt;
*[[CSC/ECE_517_Fall_2016/E1662. UI issues/fixes]]&lt;/div&gt;</summary>
		<author><name>Psabhyan</name></author>
	</entry>
</feed>