CSC/ECE 517 Spring 2017 E1714 - Revision history

Admin: /* Solution */

2017-04-04T15:45:59Z

Solution

← Older revision		Revision as of 15:45, 4 April 2017
Line 7:		Line 7:

	An instructor can view a list of all the topics for any given assignment. Each topic shows any signed up teams and whether students are signed up or waitlisted. The proposed change introduces a new button next to each team that allows an instructor to remove a team from a topic. In this manner, an instructor can drop a team from a topic with relative ease.		An instructor can view a list of all the topics for any given assignment. Each topic shows any signed up teams and whether students are signed up or waitlisted. The proposed change introduces a new button next to each team that allows an instructor to remove a team from a topic. In this manner, an instructor can drop a team from a topic with relative ease.
	An additional button was also implemented to give an instructor the option to ~~signup~~ a specific team for a topic. An instructor can select a team by specifying one of the team members. If the student specified by the instructor is not part of a team, a team is created for the student as part of the signup process. The signup button is located in the topic name box and redirects to a new page. The new page contains a form where the instructor can enter a student's name. Once a team is added, the instructor is redirected back to the edit assignment page where the topic is updated with the specified student's team.		An additional button was also implemented to give an instructor the option to sign a specific team up for a topic. An instructor can select a team by specifying one of the team members. If the student specified by the instructor is not part of a team, a team is created for the student as part of the signup process. The signup button is located in the topic name box and redirects to a new page. The new page contains a form where the instructor can enter a student's name. Once a team is added, the instructor is redirected back to the edit assignment page where the topic is updated with the specified student's team.

	== Expected Functionality ==		== Expected Functionality ==

Srashid3: /* signup_sheet_controller.rb */

2017-04-01T01:52:30Z

signup_sheet_controller.rb

← Older revision		Revision as of 01:52, 1 April 2017
Line 122:		Line 122:

	=== signup_sheet_controller.rb ===		=== signup_sheet_controller.rb ===
	The signup_sheet_controller is where most of the new functionality is introduced.		The signup_sheet_controller is where most of the new functionality is introduced. These functions are based on the existing signup and delete actions, but are modified to match the context an instructor is given. For example, the signup action validates the user the instructor supplies and no longer uses the session user. Similarly for the delete action, the user must be extracted from the team ID. The flash messages were also modified to notify an instructor rather than a student.

	<code>		<code>

Srashid3: /* signup_as_instructor.html.erb */

2017-04-01T01:45:31Z

signup_as_instructor.html.erb

← Older revision		Revision as of 01:45, 1 April 2017
Line 110:		Line 110:

	=== signup_as_instructor.html.erb ===		=== signup_as_instructor.html.erb ===
			This additional view renders a form where the instructor can specify a student for the signup action. The instructor is redirected to this page after clicking the signup link in the topic names partial.
	<code>		<code>
	<%= form_tag(:controller => "sign_up_sheet", :action => "signup_as_instructor_action",:topic_id => params[:topic_id], :assignment_id => params[:assignment_id]) do %>		<%= form_tag(:controller => "sign_up_sheet", :action => "signup_as_instructor_action",:topic_id => params[:topic_id], :assignment_id => params[:assignment_id]) do %>

Srashid3: /* _topic_name.html.erb */

2017-04-01T01:42:02Z

_topic_name.html.erb

← Older revision		Revision as of 01:42, 1 April 2017
Line 102:		Line 102:
	=== _topic_name.html.erb ===		=== _topic_name.html.erb ===

	The topic_name partial is the primary view for this feature. It renders the table cell where the topic, team, and students are listed. The following ~~code was modified~~:		The topic_name partial is the primary view for this feature. It renders the table cell where the topic, team, and students are listed. The following links were added to the partial where appropriate:
	<code>		<code>
	<%= link_to image_tag('signup.png', :border => 0, :title => 'Sign Up Student', :align => 'middle'), signup_as_instructor_sign_up_sheet_index_path( assignment_id: params[:id], topic_id: topic.id) %>		<%= link_to image_tag('signup.png', :border => 0, :title => 'Sign Up Student', :align => 'middle'), signup_as_instructor_sign_up_sheet_index_path( assignment_id: params[:id], topic_id: topic.id) %>
	<%= link_to image_tag('leave_topic.png', :border => 0, :title => 'Drop Student', :align => 'middle'), :controller => "sign_up_sheet", :action => "delete_signup_as_instructor", :id => participant.team_id, :topic_id => topic.id %>		<%= link_to image_tag('leave_topic.png', :border => 0, :title => 'Drop Student', :align => 'middle'), :controller => "sign_up_sheet", :action => "delete_signup_as_instructor", :id => participant.team_id, :topic_id => topic.id %>
	</code>		</code>
	~~The~~ instructor will see a different set of links depending on whether or not a team has already been assigned to a topic. If no team is present, only a single link that adds a student and their team will be visible. If a team is already present, then an additional link that drops that existing team will be visible. In this ~~case~~, the signup link will add students to the waitlist instead.		Note that the instructor will see a different set of links depending on whether or not a team has already been assigned to a topic. If no team is present, only a single link that adds a student and their team will be visible. If a team is already present, then an additional link that drops that existing team will be visible. In this scenario, the signup link will add students to the waitlist instead.

	=== signup_as_instructor.html.erb ===		=== signup_as_instructor.html.erb ===

Srashid3: /* Solution */

2017-04-01T01:39:44Z

Solution

← Older revision		Revision as of 01:39, 1 April 2017
Line 7:		Line 7:

	An instructor can view a list of all the topics for any given assignment. Each topic shows any signed up teams and whether students are signed up or waitlisted. The proposed change introduces a new button next to each team that allows an instructor to remove a team from a topic. In this manner, an instructor can drop a team from a topic with relative ease.		An instructor can view a list of all the topics for any given assignment. Each topic shows any signed up teams and whether students are signed up or waitlisted. The proposed change introduces a new button next to each team that allows an instructor to remove a team from a topic. In this manner, an instructor can drop a team from a topic with relative ease.
	~~Next, an~~ additional button was implemented to give an instructor the option to signup a specific team for a topic. An instructor can select a team by specifying one of the team members. If the student specified by the instructor is not part of a team, a team is created for the student as part of the signup process. The signup button is located in the topic name box and redirects to a new page. The new page contains a form where the instructor can enter a student's name. Once a team is added, the instructor is redirected back to the edit assignment page where the topic is updated with the specified student's team.		An additional button was also implemented to give an instructor the option to signup a specific team for a topic. An instructor can select a team by specifying one of the team members. If the student specified by the instructor is not part of a team, a team is created for the student as part of the signup process. The signup button is located in the topic name box and redirects to a new page. The new page contains a form where the instructor can enter a student's name. Once a team is added, the instructor is redirected back to the edit assignment page where the topic is updated with the specified student's team.

	== Expected Functionality ==		== Expected Functionality ==

Srashid3: Undo revision 107777 by Srashid3 (talk)

2017-04-01T01:38:58Z

Undo revision 107777 by Srashid3 (talk)

← Older revision		Revision as of 01:38, 1 April 2017
Line 7:		Line 7:

	An instructor can view a list of all the topics for any given assignment. Each topic shows any signed up teams and whether students are signed up or waitlisted. The proposed change introduces a new button next to each team that allows an instructor to remove a team from a topic. In this manner, an instructor can drop a team from a topic with relative ease.		An instructor can view a list of all the topics for any given assignment. Each topic shows any signed up teams and whether students are signed up or waitlisted. The proposed change introduces a new button next to each team that allows an instructor to remove a team from a topic. In this manner, an instructor can drop a team from a topic with relative ease.
	An additional button ~~also~~ was implemented to give an instructor the option to signup a specific team for a topic. An instructor can select a team by specifying one of the team members. If the student specified by the instructor is not part of a team, a team is created for the student as part of the signup process. The signup button is located in the topic name box and redirects to a new page. The new page contains a form where the instructor can enter a student's name. Once a team is added, the instructor is redirected back to the edit assignment page where the topic is updated with the specified student's team.		Next, an additional button was implemented to give an instructor the option to signup a specific team for a topic. An instructor can select a team by specifying one of the team members. If the student specified by the instructor is not part of a team, a team is created for the student as part of the signup process. The signup button is located in the topic name box and redirects to a new page. The new page contains a form where the instructor can enter a student's name. Once a team is added, the instructor is redirected back to the edit assignment page where the topic is updated with the specified student's team.

	== Expected Functionality ==		== Expected Functionality ==

Srashid3: /* Solution */

2017-04-01T01:38:18Z

Solution

← Older revision		Revision as of 01:38, 1 April 2017
Line 7:		Line 7:

	An instructor can view a list of all the topics for any given assignment. Each topic shows any signed up teams and whether students are signed up or waitlisted. The proposed change introduces a new button next to each team that allows an instructor to remove a team from a topic. In this manner, an instructor can drop a team from a topic with relative ease.		An instructor can view a list of all the topics for any given assignment. Each topic shows any signed up teams and whether students are signed up or waitlisted. The proposed change introduces a new button next to each team that allows an instructor to remove a team from a topic. In this manner, an instructor can drop a team from a topic with relative ease.
	~~Next, an~~ additional button was implemented to give an instructor the option to signup a specific team for a topic. An instructor can select a team by specifying one of the team members. If the student specified by the instructor is not part of a team, a team is created for the student as part of the signup process. The signup button is located in the topic name box and redirects to a new page. The new page contains a form where the instructor can enter a student's name. Once a team is added, the instructor is redirected back to the edit assignment page where the topic is updated with the specified student's team.		An additional button also was implemented to give an instructor the option to signup a specific team for a topic. An instructor can select a team by specifying one of the team members. If the student specified by the instructor is not part of a team, a team is created for the student as part of the signup process. The signup button is located in the topic name box and redirects to a new page. The new page contains a form where the instructor can enter a student's name. Once a team is added, the instructor is redirected back to the edit assignment page where the topic is updated with the specified student's team.

	== Expected Functionality ==		== Expected Functionality ==

Srashid3: /* Peer Review Information */

2017-04-01T01:32:12Z

Peer Review Information

← Older revision		Revision as of 01:32, 1 April 2017
Line 75:		Line 75:
	*** Ensure the "Participant" radio button is selected		*** Ensure the "Participant" radio button is selected
	*** Select add		*** Select add
	* ~~Reaching~~ assignment topics page		* Navigating to the assignment topics page
	** Login as an instructor		** Login as an instructor
	** In the top red navigation bar, choose "Manage"		** In the top red navigation bar, choose "Manage"

Srashid3: /* Testing */

2017-04-01T01:28:47Z

Testing

← Older revision		Revision as of 01:28, 1 April 2017
Line 167:		Line 167:
	== Testing ==		== Testing ==

	Since we added new functionality, we needed to create new preconditions for testing ~~the functionality~~. We describe the preconditions below.		Since we added new functionality, we needed to create new preconditions for testing. We describe the preconditions below.
	~~Rspec~~ is utilized to perform the unit tests under the spec/controllers/sign_up_sheet_spec.rb file. We do not test ~~the functionality of~~ adding multiple students ~~as this~~ is tested in existing ~~functionality that we utilized~~. We can assume that signing up a student will sign up the whole team as indicated by the contract with the existing function. The same contract exists for removing a student's sign up. We also wish to make a distinction in the goal of our functionality. It is not to remove one student from the team. It is to remove the whole team from a topic. ~~Addition~~ of too much extra functionality ~~because it may be nice~~ will clutter the system, thus we don't implement or test the addition or removal of an individual from a team since it is implemented elsewhere.		RSpec is utilized to perform the unit tests under the spec/controllers/sign_up_sheet_spec.rb file. We do not test adding multiple students since it is already tested with existing functions. We can assume that signing up a student will sign up the whole team as indicated by the contract with the existing function. The same contract exists for removing a student's sign up. We also wish to make a distinction in the goal of our functionality. It is not to remove one student from the team. It is to remove the whole team from a topic. The addition of too much extra functionality will clutter the system, thus we don't implement or test the addition or removal of an individual from a team since it is implemented elsewhere.

	=====~~Preconditions~~=====		=====Pre-Conditions=====
	We create ~~a three~~ students and an instructor. We also create an assignment to which ~~we add~~ the ~~three~~ students as participants. ~~Three~~ teams are created with ~~one user~~ assigned to ~~each team~~. The ~~third~~ team is ~~created such that it has already~~ submitted ~~it's work~~. ~~Three~~ topics are created ~~for~~ the assignment ~~with deadlines~~. ~~The second and third teams are~~ signed up ~~for topics two~~ and ~~three. The instructor~~ is to ~~add~~ the ~~first student to topic one created for the assignment~~. The ~~instructor~~ is ~~also to attempt to remove team two and three from being~~ signed up.		We create two students and an instructor. We also create an assignment which adds the two students as participants. Two teams are created with a student assigned to one of the teams. The other team is used for tests where no work is submitted. Two topics are created and use the assignment deadline. One student is signed up to a topic and is used to test the delete functionality. The other student is signed up by the instructor and tests the signup functionality. The objects are refreshed before each test.
	The objects are refreshed each ~~time~~.

	{\| class="wikitable"		{\| class="wikitable"

Srashid3: Formatting

2017-04-01T00:58:22Z

Formatting

← Older revision		Revision as of 00:58, 1 April 2017
Line 10:		Line 10:

	== Expected Functionality ==		== Expected Functionality ==
	=== Instructor ~~Signs Up~~ a ~~Student For~~ a ~~Topic~~ ===		=== Instructor signs up a student for a topic ===
	From the instructor's edit assignments page with the tab topics selected, the instructor should see a list of topics for the given assignment.		From the instructor's edit assignments page with the tab topics selected, the instructor should see a list of topics for the given assignment.
	For each topic, the instructor should be able to:		For each topic, the instructor should be able to:
Line 21:		Line 21:
	** The team should be added to the end of the waitlist		** The team should be added to the end of the waitlist

	Each action is performed by choosing the green checkmark next to the desired topic name		Each action is performed by choosing the green checkmark next to the desired topic name.

	=== Instructor removes a student's signup for a topic ===		=== Instructor removes a student's signup for a topic ===
Line 32:		Line 32:
	** The team should be removed from the waitlist		** The team should be removed from the waitlist

	Each action is done by choosing the x enclosed by a red circle next to the desired team		Each action is done by choosing the X enclosed by a red circle next to the desired team.

	== Peer Review Information ==		== Peer Review Information ==
	Please review the information below ~~for further information~~ on how to ~~review~~ the ~~modifications made~~.		Please review the information below on how to manually test the implemented changes.

	Login Information:		Login Information:
Line 69:		Line 69:
	** Log in as an instructor		** Log in as an instructor
	** Go to "Courses" tab to add a student to a course, go to "Assignments" tab to add a student to an assignment		** Go to "Courses" tab to add a student to a course, go to "Assignments" tab to add a student to an assignment
	** Choose "Add Participants" button under "Actions" column. It appears as a person wearing a blue shirt with a ~~gree~~ plus above them		** Choose "Add Participants" button under "Actions" column. It appears as a person wearing a blue shirt with a green plus above them
	** The list shows all users currently signed up and what role they have		** The list shows all users currently signed up and what role they have
	** Scroll to the bottom of the bottom of the page		** Scroll to the bottom of the bottom of the page
Line 77:		Line 77:
	* Reaching assignment topics page		* Reaching assignment topics page
	** Login as an instructor		** Login as an instructor
	** In the top red navigation bar, choose "Manage.."		** In the top red navigation bar, choose "Manage"
	** Select "Assignments" above the search bar		** Select "Assignments" above the search bar
	** Click the pencil button under actions column for any assignment		** Click the pencil button under actions column for any assignment
Line 100:		Line 100:
	== Modifications ==		== Modifications ==

	=== ~~sign_up_sheet/~~_topic_name.html.erb ===		=== _topic_name.html.erb ===

	The topic_name partial is the primary view for this feature. It renders the table cell where the topic, team, and students are listed. The following code was modified:		The topic_name partial is the primary view for this feature. It renders the table cell where the topic, team, and students are listed. The following code was modified:
Line 109:		Line 109:
	The instructor will see a different set of links depending on whether or not a team has already been assigned to a topic. If no team is present, only a single link that adds a student and their team will be visible. If a team is already present, then an additional link that drops that existing team will be visible. In this case, the signup link will add students to the waitlist instead.		The instructor will see a different set of links depending on whether or not a team has already been assigned to a topic. If no team is present, only a single link that adds a student and their team will be visible. If a team is already present, then an additional link that drops that existing team will be visible. In this case, the signup link will add students to the waitlist instead.

	=== ~~sign_up_sheet/~~signup_as_instructor.html.erb ===		=== signup_as_instructor.html.erb ===

	<code>		<code>