Expertiza_Wiki - User contributions [en]

File:Img8 1743.jpg

2017-05-08T20:20:17Z

Fsmisarw: Updated Image on test cases

Updated Image on test cases

CSC/ECE 517 Spring 2017/E1743

2017-05-08T20:18:40Z

Fsmisarw: /* Test Plan */

== Problem Statement 1 ==

Expertiza has a feature that allows instructor i (or an admin) to impersonate a user whose account was created by i or recursively by a user that i created. This causes Expertiza to show what the impersonated user would see. It is good for tracking down bugs in what students see and also for accessing functionality that cannot be accessed from, or is too slow to access from, the instructor UI. Impersonating is currently performed by going to the pull-down menu at the top of the window and selecting Manage > Impersonate user. However, usually the instructor initiates impersonation after finding the student in some kind of list, like a list of users, or assignment participants, or as a member of a team signed up for a topic, etc. In this case, it is inconvenient to have to go to the pulldown menu and type in the user ID. It would be better if the instructor could just click on the ID in the list, and immediately have the impersonated user’s homepage show up.

Here’s what it looks like:

[[File:Img1_1743.JPG|center|Screenshot of the current Impersonate User page]]

The idea is to have more convenient options for instructors where a list of students is available, making it easier to both impersonate and view the details of any student with direct links.

== Implementation 1 ==

[[File:Img2_1743_new.jpg|center|Solution for Impersonate User links]]

We have made the following changes to the system as shown by the screenshot above.

Red: The student ID previously had a link that directs to the user profile page. We have changed that to a link that would impersonate the user immediately. We did this by calling the impersonate function directly from this page and passing the user's ID as a parameter.

Blue: The user profile page link was shifted to this column instead. This column originally did not have any link on it.

Green: A link on the email address which now invokes a mailto: HTML link. This column also previously did not have any links.

The following screens did not previously show the user-ID, but we have modified them to do so.

- View scores (User IDs could be shown below names in the Contributor column.)

- View review report

- Author feedback report (available from the pull-down menu on Review report).

- Teammate review report ( “ “ “)

All these pages display some part of the user model, meaning they have all the data from the model. So, it was just a matter of displaying the appropriate user-ID.

'''Changes:'''

The changes we made on this part are the addition of lines printing the user-ID, and it was presented with a link which calls the impersonate function, using the user's ID as a parameter. The following snippet of code shows the exact lines we have changed.
We have also switched the user profile link from the user-ID (what it was originally) to the user's full name.
A mailto: HTML link has been added on the email address which generates a pop-up with the email ID.

[[File:Img4_1743.jpg|center|Code for Impersonate User links]]

== Problem Statement 2 ==

The '''second problem''' is that originally, the default for Manage > Users was to list all 6000+ users on one page, which lead to long delays. The default should be to show the first 25 users and there should be options to list 100, 250, or all users.

'''Purpose:'''
The reason behind adding this feature is also to make it the list of users easier to read, possibly reduce retrieval and loading time, and improve ease of navigation.

== Implementation 2 ==

[[File:Img3_1743_new.jpg|center|Solution for division and navigation of pages]]

The yellow portion in the above screenshot is where we have added options to display 25, 100, 250, or all users at once, along with links to ‘previous’ and ‘next’ pages.

'''Changes:'''

There is a gem called will_paginate that adds a pagination library which integrates with ruby on rails. That gem is already added to the gemfile of expertiza, but was not used in this particular page. Once added, it provides a paginate method which automatically generates a paginated list with a per_page parameter. Then that list is passed to the view, which automatically displays the necessary links such as “previous”, “next”, individual page links, etc

We have reduced the complexity of the logic that was originally implemented. Previously, it populated the user list by querying the course and assignment models.

Here's what the code originally looked like:

[[File:Img5_1743.jpg|center|Original code for user.rb]]

As suggested by Dr. Gehringer, we add a user to the user list array only if the currently logged in user is able to impersonate them.

Here's what we have changed that to:

[[File:Img6_1743.png|center|New code for user.rb]]

== Test Plan ==

Most of the testing for this project is fairly simple.

'''Manual:'''

Problem 1:
All of the altered links will need to be tested to ensure they link to the correct pages. Tests that check if the username link correctly initiates impersonation of that user, and that clicking the full name links to the right user profile.

A test user needs to be created and the email link will be used to ensure emails are correctly sent.

Problem 2:
For the second part of the project, tests need to be set up to check that the correct number of students are being displayed for each display option, and that the user can display subsequent pages of users.

'''Automated:'''

Problem 1 includes changes in view files. Hence, we are not planning to create automated test cases for problem 1.

Problem 2:
Unit Tests: We will add unit test cases in user_spec.rb.
Case I:
Condition: page number = 4 and per page option = 25
Result: Ensure users list contain 25 entries.
Case II:
Condition: page number = 1 and per page option = 50
Result: Ensure users list contain all entries.

Here's what we have added in the user_spec.rb file as test cases.

[[File:Img7_1743.jpg|center|New code for user_spec.rb]]

A summary of the above code:

Firstly, the objects for the user, instructor, and admin are created. In the subsequent lines, we create mocks for the impersonation logic to move the test forward. In the third part, the logic is actually tested.

Lines 74 to 83 test as an instructor, while lines 85 to 94 test as a super admin. A new object for a super admin was added in factories.rb

[[File:Img8_1743.jpg|center|Test Code]]

Also, we have added automated test case for negative scenario. In this case instructor is unable to impersonate any user and thus get_user_list method in user.rb returns an empty user list array.

CSC/ECE 517 Spring 2017/E1743

2017-05-08T00:20:05Z

Fsmisarw: /* Test Plan */

CSC/ECE 517 Spring 2017/E1743

2017-05-08T00:18:11Z

Fsmisarw: /* Test Plan */

CSC/ECE 517 Spring 2017/E1743

2017-05-08T00:15:49Z

Fsmisarw:

CSC/ECE 517 Spring 2017/E1743

2017-05-08T00:15:12Z

Fsmisarw: /* Implementation */

== Problem Statement 1 ==

Expertiza has a feature that allows instructor i (or an admin) to impersonate a user whose account was created by i or recursively by a user that i created. This causes Expertiza to show what the impersonated user would see. It is good for tracking down bugs in what students see and also for accessing functionality that cannot be accessed from, or is too slow to access from, the instructor UI. Impersonating is currently performed by going to the pull-down menu at the top of the window and selecting Manage > Impersonate user. However, usually the instructor initiates impersonation after finding the student in some kind of list, like a list of users, or assignment participants, or as a member of a team signed up for a topic, etc. In this case, it is inconvenient to have to go to the pulldown menu and type in the user ID. It would be better if the instructor could just click on the ID in the list, and immediately have the impersonated user’s homepage show up.

Here’s what it looks like:

[[File:Img1_1743.JPG|center|Screenshot of the current Impersonate User page]]

The idea is to have more convenient options for instructors where a list of students is available, making it easier to both impersonate and view the details of any student with direct links.

== Solution 1 ==

[[File:Img2_1743_new.jpg|center|Solution for Impersonate User links]]

We have made the following changes to the system as shown by the screenshot above.

Red: The student ID previously had a link that directs to the user profile page. We have changed that to a link that would impersonate the user immediately. We did this by calling the impersonate function directly from this page and passing the user's ID as a parameter.

Blue: The user profile page link was shifted to this column instead. This column originally did not have any link on it.

Green: A link on the email address which now invokes a mailto: HTML link. This column also previously did not have any links.

The following screens did not previously show the user-ID, but we have modified them to do so.

- View scores (User IDs could be shown below names in the Contributor column.)

- View review report

- Author feedback report (available from the pull-down menu on Review report).

- Teammate review report ( “ “ “)

All these pages display some part of the user model, meaning they have all the data from the model. So, it was just a matter of displaying the appropriate user-ID.

'''Changes:'''

The changes we made on this part are the addition of lines printing the user-ID, and it was presented with a link which calls the impersonate function, using the user's ID as a parameter. The following snippet of code shows the exact lines we have changed.
We have also switched the user profile link from the user-ID (what it was originally) to the user's full name.
A mailto: HTML link has been added on the email address which generates a pop-up with the email ID.

[[File:Img4_1743.jpg|center|Code for Impersonate User links]]

== Problem Statement 2 ==

The '''second problem''' is that originally, the default for Manage > Users was to list all 6000+ users on one page, which lead to long delays. The default should be to show the first 25 users and there should be options to list 100, 250, or all users.

'''Purpose:'''
The reason behind adding this feature is also to make it the list of users easier to read, possibly reduce retrieval and loading time, and improve ease of navigation.

== Solution 2 ==

[[File:Img3_1743_new.jpg|center|Solution for division and navigation of pages]]

The yellow portion in the above screenshot is where we have added options to display 25, 100, 250, or all users at once, along with links to ‘previous’ and ‘next’ pages.

'''Changes:'''

There is a gem called will_paginate that adds a pagination library which integrates with ruby on rails. That gem is already added to the gemfile of expertiza, but was not used in this particular page. Once added, it provides a paginate method which automatically generates a paginated list with a per_page parameter. Then that list is passed to the view, which automatically displays the necessary links such as “previous”, “next”, individual page links, etc

We have reduced the complexity of the logic that was originally implemented. Previously, it populated the user list by querying the course and assignment models.

Here's what the code originally looked like:

[[File:Img5_1743.jpg|center|Original code for user.rb]]

As suggested by Dr. Gehringer, we add a user to the user list array only if the currently logged in user is able to impersonate them.

Here's what we have changed that to:

[[File:Img6_1743.png|center|New code for user.rb]]

== Test Plan ==

Most of the testing for this project is fairly simple.

'''Manual:'''

Problem 1:
All of the altered links will need to be tested to ensure they link to the correct pages. Tests that check if the username link correctly initiates impersonation of that user, and that clicking the full name links to the right user profile.

A test user needs to be created and the email link will be used to ensure emails are correctly sent.

Problem 2:
For the second part of the project, tests need to be set up to check that the correct number of students are being displayed for each display option, and that the user can display subsequent pages of users.

'''Automated:'''

Problem 1 includes changes in view files. Hence, we are not planning to create automated test cases for problem 1.

Problem 2:
Unit Tests: We will add unit test cases in user_spec.rb.
Case I:
Condition: page number = 4 and per page option = 25
Result: Ensure users list contain 25 entries.
Case II:
Condition: page number = 1 and per page option = 50
Result: Ensure users list contain all entries.

Here's what we have added in the user_spec.rb file as test cases.

[[File:Img7_1743.jpg|center|New code for user_spec.rb]]

CSC/ECE 517 Spring 2017/E1743

2017-05-08T00:14:14Z

Fsmisarw: /* Solution 2 */

== Problem Statement 1 ==

Expertiza has a feature that allows instructor i (or an admin) to impersonate a user whose account was created by i or recursively by a user that i created. This causes Expertiza to show what the impersonated user would see. It is good for tracking down bugs in what students see and also for accessing functionality that cannot be accessed from, or is too slow to access from, the instructor UI. Impersonating is currently performed by going to the pull-down menu at the top of the window and selecting Manage > Impersonate user. However, usually the instructor initiates impersonation after finding the student in some kind of list, like a list of users, or assignment participants, or as a member of a team signed up for a topic, etc. In this case, it is inconvenient to have to go to the pulldown menu and type in the user ID. It would be better if the instructor could just click on the ID in the list, and immediately have the impersonated user’s homepage show up.

Here’s what it looks like:

[[File:Img1_1743.JPG|center|Screenshot of the current Impersonate User page]]

The idea is to have more convenient options for instructors where a list of students is available, making it easier to both impersonate and view the details of any student with direct links.

== Solution 1 ==

[[File:Img2_1743_new.jpg|center|Solution for Impersonate User links]]

We have made the following changes to the system as shown by the screenshot above.

Red: The student ID previously had a link that directs to the user profile page. We have changed that to a link that would impersonate the user immediately. We did this by calling the impersonate function directly from this page and passing the user's ID as a parameter.

Blue: The user profile page link was shifted to this column instead. This column originally did not have any link on it.

Green: A link on the email address which now invokes a mailto: HTML link. This column also previously did not have any links.

The following screens did not previously show the user-ID, but we have modified them to do so.

- View scores (User IDs could be shown below names in the Contributor column.)

- View review report

- Author feedback report (available from the pull-down menu on Review report).

- Teammate review report ( “ “ “)

All these pages display some part of the user model, meaning they have all the data from the model. So, it was just a matter of displaying the appropriate user-ID.

'''Changes:'''

The changes we made on this part are the addition of lines printing the user-ID, and it was presented with a link which calls the impersonate function, using the user's ID as a parameter. The following snippet of code shows the exact lines we have changed.
We have also switched the user profile link from the user-ID (what it was originally) to the user's full name.
A mailto: HTML link has been added on the email address which generates a pop-up with the email ID.

[[File:Img4_1743.jpg|center|Code for Impersonate User links]]

== Problem Statement 2 ==

The '''second problem''' is that originally, the default for Manage > Users was to list all 6000+ users on one page, which lead to long delays. The default should be to show the first 25 users and there should be options to list 100, 250, or all users.

'''Purpose:'''
The reason behind adding this feature is also to make it the list of users easier to read, possibly reduce retrieval and loading time, and improve ease of navigation.

== Solution 2 ==

[[File:Img3_1743_new.jpg|center|Solution for division and navigation of pages]]

The yellow portion in the above screenshot is where we have added options to display 25, 100, 250, or all users at once, along with links to ‘previous’ and ‘next’ pages.

'''Changes:'''

There is a gem called will_paginate that adds a pagination library which integrates with ruby on rails. That gem is already added to the gemfile of expertiza, but was not used in this particular page. Once added, it provides a paginate method which automatically generates a paginated list with a per_page parameter. Then that list is passed to the view, which automatically displays the necessary links such as “previous”, “next”, individual page links, etc

We have reduced the complexity of the logic that was originally implemented. Previously, it populated the user list by querying the course and assignment models.

Here's what the code originally looked like:

[[File:Img5_1743.jpg|center|Original code for user.rb]]

As suggested by Dr. Gehringer, we add a user to the user list array only if the currently logged in user is able to impersonate them.

Here's what we have changed that to:

[[File:Img6_1743.png|center|New code for user.rb]]

== Implementation ==
The following files have been modified:

Models:

- user.rb

Controllers:

- users_controller.rb

Views:

- users/list.html.erb

- assignments/list_submissions.html.erb

- grades/view.html.erb

- review_mapping/response_report.html.haml

- assessment360/all_students_all_reviews.html.erb

== Test Plan ==

Most of the testing for this project is fairly simple.

'''Manual:'''

Problem 1:
All of the altered links will need to be tested to ensure they link to the correct pages. Tests that check if the username link correctly initiates impersonation of that user, and that clicking the full name links to the right user profile.

A test user needs to be created and the email link will be used to ensure emails are correctly sent.

Problem 2:
For the second part of the project, tests need to be set up to check that the correct number of students are being displayed for each display option, and that the user can display subsequent pages of users.

'''Automated:'''

Problem 1 includes changes in view files. Hence, we are not planning to create automated test cases for problem 1.

Problem 2:
Unit Tests: We will add unit test cases in user_spec.rb.
Case I:
Condition: page number = 4 and per page option = 25
Result: Ensure users list contain 25 entries.
Case II:
Condition: page number = 1 and per page option = 50
Result: Ensure users list contain all entries.

Here's what we have added in the user_spec.rb file as test cases.

[[File:Img7_1743.jpg|center|New code for user_spec.rb]]

CSC/ECE 517 Spring 2017/E1743

2017-05-08T00:10:44Z

Fsmisarw: /* Solution 1 */

== Problem Statement 1 ==

Expertiza has a feature that allows instructor i (or an admin) to impersonate a user whose account was created by i or recursively by a user that i created. This causes Expertiza to show what the impersonated user would see. It is good for tracking down bugs in what students see and also for accessing functionality that cannot be accessed from, or is too slow to access from, the instructor UI. Impersonating is currently performed by going to the pull-down menu at the top of the window and selecting Manage > Impersonate user. However, usually the instructor initiates impersonation after finding the student in some kind of list, like a list of users, or assignment participants, or as a member of a team signed up for a topic, etc. In this case, it is inconvenient to have to go to the pulldown menu and type in the user ID. It would be better if the instructor could just click on the ID in the list, and immediately have the impersonated user’s homepage show up.

Here’s what it looks like:

[[File:Img1_1743.JPG|center|Screenshot of the current Impersonate User page]]

The idea is to have more convenient options for instructors where a list of students is available, making it easier to both impersonate and view the details of any student with direct links.

== Solution 1 ==

[[File:Img2_1743_new.jpg|center|Solution for Impersonate User links]]

We have made the following changes to the system as shown by the screenshot above.

Red: The student ID previously had a link that directs to the user profile page. We have changed that to a link that would impersonate the user immediately. We did this by calling the impersonate function directly from this page and passing the user's ID as a parameter.

Blue: The user profile page link was shifted to this column instead. This column originally did not have any link on it.

Green: A link on the email address which now invokes a mailto: HTML link. This column also previously did not have any links.

The following screens did not previously show the user-ID, but we have modified them to do so.

- View scores (User IDs could be shown below names in the Contributor column.)

- View review report

- Author feedback report (available from the pull-down menu on Review report).

- Teammate review report ( “ “ “)

All these pages display some part of the user model, meaning they have all the data from the model. So, it was just a matter of displaying the appropriate user-ID.

'''Changes:'''

The changes we made on this part are the addition of lines printing the user-ID, and it was presented with a link which calls the impersonate function, using the user's ID as a parameter. The following snippet of code shows the exact lines we have changed.
We have also switched the user profile link from the user-ID (what it was originally) to the user's full name.
A mailto: HTML link has been added on the email address which generates a pop-up with the email ID.

[[File:Img4_1743.jpg|center|Code for Impersonate User links]]

== Problem Statement 2 ==

The '''second problem''' is that originally, the default for Manage > Users was to list all 6000+ users on one page, which lead to long delays. The default should be to show the first 25 users and there should be options to list 100, 250, or all users.

'''Purpose:'''
The reason behind adding this feature is also to make it the list of users easier to read, possibly reduce retrieval and loading time, and improve ease of navigation.

== Solution 2 ==

[[File:Img3_1743_new.jpg|center|Solution for division and navigation of pages]]

The yellow portion in the above screenshot is where we have added options to display 25, 100, 250, or all users at once, along with links to ‘previous’ and ‘next’ pages.

'''Changes:'''

There is a gem called will_paginate that adds a pagination library which integrates with ruby on rails. That gem is already added to the gemfile of expertiza, but was not used in this particular page. Once added, it provides a paginate method which automatically generates a paginated list with a per_page parameter. Then that list is passed to the view, which automatically displays the necessary links such as “previous”, “next”, individual page links, etc

Here's what the code originally looked like:

[[File:Img5_1743.jpg|center|Original code for user.rb]]

Here's what we have changed that to:

[[File:Img6_1743.png|center|New code for user.rb]]

== Implementation ==
The following files have been modified:

Models:

- user.rb

Controllers:

- users_controller.rb

Views:

- users/list.html.erb

- assignments/list_submissions.html.erb

- grades/view.html.erb

- review_mapping/response_report.html.haml

- assessment360/all_students_all_reviews.html.erb

== Test Plan ==

Most of the testing for this project is fairly simple.

'''Manual:'''

Problem 1:
All of the altered links will need to be tested to ensure they link to the correct pages. Tests that check if the username link correctly initiates impersonation of that user, and that clicking the full name links to the right user profile.

A test user needs to be created and the email link will be used to ensure emails are correctly sent.

Problem 2:
For the second part of the project, tests need to be set up to check that the correct number of students are being displayed for each display option, and that the user can display subsequent pages of users.

'''Automated:'''

Problem 1 includes changes in view files. Hence, we are not planning to create automated test cases for problem 1.

Problem 2:
Unit Tests: We will add unit test cases in user_spec.rb.
Case I:
Condition: page number = 4 and per page option = 25
Result: Ensure users list contain 25 entries.
Case II:
Condition: page number = 1 and per page option = 50
Result: Ensure users list contain all entries.

Here's what we have added in the user_spec.rb file as test cases.

[[File:Img7_1743.jpg|center|New code for user_spec.rb]]

File:Img7 1743.jpg

2017-05-08T00:08:04Z

Fsmisarw:

CSC/ECE 517 Spring 2017/E1743

2017-05-08T00:07:55Z

Fsmisarw:

== Problem Statement 1 ==

Expertiza has a feature that allows instructor i (or an admin) to impersonate a user whose account was created by i or recursively by a user that i created. This causes Expertiza to show what the impersonated user would see. It is good for tracking down bugs in what students see and also for accessing functionality that cannot be accessed from, or is too slow to access from, the instructor UI. Impersonating is currently performed by going to the pull-down menu at the top of the window and selecting Manage > Impersonate user. However, usually the instructor initiates impersonation after finding the student in some kind of list, like a list of users, or assignment participants, or as a member of a team signed up for a topic, etc. In this case, it is inconvenient to have to go to the pulldown menu and type in the user ID. It would be better if the instructor could just click on the ID in the list, and immediately have the impersonated user’s homepage show up.

Here’s what it looks like:

[[File:Img1_1743.JPG|center|Screenshot of the current Impersonate User page]]

The idea is to have more convenient options for instructors where a list of students is available, making it easier to both impersonate and view the details of any student with direct links.

== Solution 1 ==

[[File:Img2_1743_new.jpg|center|Solution for Impersonate User links]]

We have made the following changes to the system as shown by the screenshot above.

Red: The student ID previously had a link that directs to the user profile page. We have changed that to a link that would impersonate the user immediately. We did this by calling the impersonate function directly from this page and passing the user's ID as a parameter.

Blue: The user profile page link was shifted to this column instead. This column originally did not have any link on it.

Green: A link on the email address which now invokes a mailto: HTML link. This column also previously did not have any links.

The following screens did not previously show the user-ID, but we have modified them to do so.

- View scores (User IDs could be shown below names in the Contributor column.)

- View review report

- Author feedback report (available from the pull-down menu on Review report).

- Teammate review report ( “ “ “)

All these pages display some part of the user model, meaning they have all the data from the model. So, it was just a matter of displaying the appropriate user-ID.

'''Changes:'''

The changes we made on this part are the addition of lines printing the user-ID, and it was presented with a link which calls the impersonate function, using the user's ID as a parameter. The following snippet of code shows the exact lines we have changed.

[[File:Img4_1743.jpg|center|Code for Impersonate User links]]

== Problem Statement 2 ==

The '''second problem''' is that originally, the default for Manage > Users was to list all 6000+ users on one page, which lead to long delays. The default should be to show the first 25 users and there should be options to list 100, 250, or all users.

'''Purpose:'''
The reason behind adding this feature is also to make it the list of users easier to read, possibly reduce retrieval and loading time, and improve ease of navigation.

== Solution 2 ==

[[File:Img3_1743_new.jpg|center|Solution for division and navigation of pages]]

The yellow portion in the above screenshot is where we have added options to display 25, 100, 250, or all users at once, along with links to ‘previous’ and ‘next’ pages.

'''Changes:'''

There is a gem called will_paginate that adds a pagination library which integrates with ruby on rails. That gem is already added to the gemfile of expertiza, but was not used in this particular page. Once added, it provides a paginate method which automatically generates a paginated list with a per_page parameter. Then that list is passed to the view, which automatically displays the necessary links such as “previous”, “next”, individual page links, etc

Here's what the code originally looked like:

[[File:Img5_1743.jpg|center|Original code for user.rb]]

Here's what we have changed that to:

[[File:Img6_1743.png|center|New code for user.rb]]

== Implementation ==
The following files have been modified:

Models:

- user.rb

Controllers:

- users_controller.rb

Views:

- users/list.html.erb

- assignments/list_submissions.html.erb

- grades/view.html.erb

- review_mapping/response_report.html.haml

- assessment360/all_students_all_reviews.html.erb

== Test Plan ==

Most of the testing for this project is fairly simple.

'''Manual:'''

Problem 1:
All of the altered links will need to be tested to ensure they link to the correct pages. Tests that check if the username link correctly initiates impersonation of that user, and that clicking the full name links to the right user profile.

A test user needs to be created and the email link will be used to ensure emails are correctly sent.

Problem 2:
For the second part of the project, tests need to be set up to check that the correct number of students are being displayed for each display option, and that the user can display subsequent pages of users.

'''Automated:'''

Problem 1 includes changes in view files. Hence, we are not planning to create automated test cases for problem 1.

Problem 2:
Unit Tests: We will add unit test cases in user_spec.rb.
Case I:
Condition: page number = 4 and per page option = 25
Result: Ensure users list contain 25 entries.
Case II:
Condition: page number = 1 and per page option = 50
Result: Ensure users list contain all entries.

Here's what we have added in the user_spec.rb file as test cases.

[[File:Img7_1743.jpg|center|New code for user_spec.rb]]

CSC/ECE 517 Spring 2017/E1743

2017-05-08T00:07:39Z

Fsmisarw:

== Problem Statement 1 ==

Expertiza has a feature that allows instructor i (or an admin) to impersonate a user whose account was created by i or recursively by a user that i created. This causes Expertiza to show what the impersonated user would see. It is good for tracking down bugs in what students see and also for accessing functionality that cannot be accessed from, or is too slow to access from, the instructor UI. Impersonating is currently performed by going to the pull-down menu at the top of the window and selecting Manage > Impersonate user. However, usually the instructor initiates impersonation after finding the student in some kind of list, like a list of users, or assignment participants, or as a member of a team signed up for a topic, etc. In this case, it is inconvenient to have to go to the pulldown menu and type in the user ID. It would be better if the instructor could just click on the ID in the list, and immediately have the impersonated user’s homepage show up.

Here’s what it looks like:

[[File:Img1_1743.JPG|center|Screenshot of the current Impersonate User page]]

The idea is to have more convenient options for instructors where a list of students is available, making it easier to both impersonate and view the details of any student with direct links.

== Solution 1 ==

[[File:Img2_1743_new.jpg|center|Solution for Impersonate User links]]

We have made the following changes to the system as shown by the screenshot above.

Red: The student ID previously had a link that directs to the user profile page. We have changed that to a link that would impersonate the user immediately. We did this by calling the impersonate function directly from this page and passing the user's ID as a parameter.

Blue: The user profile page link was shifted to this column instead. This column originally did not have any link on it.

Green: A link on the email address which now invokes a mailto: HTML link. This column also previously did not have any links.

The following screens did not previously show the user-ID, but we have modified them to do so.

- View scores (User IDs could be shown below names in the Contributor column.)

- View review report

- Author feedback report (available from the pull-down menu on Review report).

- Teammate review report ( “ “ “)

All these pages display some part of the user model, meaning they have all the data from the model. So, it was just a matter of displaying the appropriate user-ID.

'''Changes:'''

The changes we made on this part are the addition of lines printing the user-ID, and it was presented with a link which calls the impersonate function, using the user's ID as a parameter. The following snippet of code shows the exact lines we have changed.

[[File:Img4_1743.jpg|center|Code for Impersonate User links]]

== Problem Statement 2 ==

The '''second problem''' is that originally, the default for Manage > Users was to list all 6000+ users on one page, which lead to long delays. The default should be to show the first 25 users and there should be options to list 100, 250, or all users.

'''Purpose:'''
The reason behind adding this feature is also to make it the list of users easier to read, possibly reduce retrieval and loading time, and improve ease of navigation.

== Solution 2 ==

[[File:Img3_1743_new.jpg|center|Solution for division and navigation of pages]]

The yellow portion in the above screenshot is where we have added options to display 25, 100, 250, or all users at once, along with links to ‘previous’ and ‘next’ pages.

'''Changes:'''

There is a gem called will_paginate that adds a pagination library which integrates with ruby on rails. That gem is already added to the gemfile of expertiza, but was not used in this particular page. Once added, it provides a paginate method which automatically generates a paginated list with a per_page parameter. Then that list is passed to the view, which automatically displays the necessary links such as “previous”, “next”, individual page links, etc

Here's what the code originally looked like:

[[File:Img5_1743.jpg|center|Original code for user.rb]]

Here's what we have changed that to:

[[File:Img6_1743.png|center|New code for user.rb]]

== Implementation ==
The following files have been modified:

Models:

- user.rb

Controllers:

- users_controller.rb

Views:

- users/list.html.erb

- assignments/list_submissions.html.erb

- grades/view.html.erb

- review_mapping/response_report.html.haml

- assessment360/all_students_all_reviews.html.erb

== Test Plan ==

Most of the testing for this project is fairly simple.

'''Manual:'''

Problem 1:
All of the altered links will need to be tested to ensure they link to the correct pages. Tests that check if the username link correctly initiates impersonation of that user, and that clicking the full name links to the right user profile.

A test user needs to be created and the email link will be used to ensure emails are correctly sent.

Problem 2:
For the second part of the project, tests need to be set up to check that the correct number of students are being displayed for each display option, and that the user can display subsequent pages of users.

'''Automated:'''

Problem 1 includes changes in view files. Hence, we are not planning to create automated test cases for problem 1.

Problem 2:
Unit Tests: We will add unit test cases in user_spec.rb.
Case I:
Condition: page number = 4 and per page option = 25
Result: Ensure users list contain 25 entries.
Case II:
Condition: page number = 1 and per page option = 50
Result: Ensure users list contain all entries.

Here's what we have added in the user_spec.rb file as test cases.

[[File:Img7_1743.png|center|New code for user.rb]]

CSC/ECE 517 Spring 2017/E1743

2017-05-08T00:04:29Z

Fsmisarw:

== Problem Statement 1 ==

Expertiza has a feature that allows instructor i (or an admin) to impersonate a user whose account was created by i or recursively by a user that i created. This causes Expertiza to show what the impersonated user would see. It is good for tracking down bugs in what students see and also for accessing functionality that cannot be accessed from, or is too slow to access from, the instructor UI. Impersonating is currently performed by going to the pull-down menu at the top of the window and selecting Manage > Impersonate user. However, usually the instructor initiates impersonation after finding the student in some kind of list, like a list of users, or assignment participants, or as a member of a team signed up for a topic, etc. In this case, it is inconvenient to have to go to the pulldown menu and type in the user ID. It would be better if the instructor could just click on the ID in the list, and immediately have the impersonated user’s homepage show up.

Here’s what it looks like:

[[File:Img1_1743.JPG|center|Screenshot of the current Impersonate User page]]

The idea is to have more convenient options for instructors where a list of students is available, making it easier to both impersonate and view the details of any student with direct links.

== Solution 1 ==

[[File:Img2_1743_new.jpg|center|Solution for Impersonate User links]]

We have made the following changes to the system as shown by the screenshot above.

Red: The student ID previously had a link that directs to the user profile page. We have changed that to a link that would impersonate the user immediately. We did this by calling the impersonate function directly from this page and passing the user's ID as a parameter.

Blue: The user profile page link was shifted to this column instead. This column originally did not have any link on it.

Green: A link on the email address which now invokes a mailto: HTML link. This column also previously did not have any links.

The following screens did not previously show the user-ID, but we have modified them to do so.

- View scores (User IDs could be shown below names in the Contributor column.)

- View review report

- Author feedback report (available from the pull-down menu on Review report).

- Teammate review report ( “ “ “)

All these pages display some part of the user model, meaning they have all the data from the model. So, it was just a matter of displaying the appropriate user-ID.

'''Changes:'''

The changes we made on this part are the addition of lines printing the user-ID, and it was presented with a link which calls the impersonate function, using the user's ID as a parameter. The following snippet of code shows the exact lines we have changed.

[[File:Img4_1743.jpg|center|Code for Impersonate User links]]

== Problem Statement 2 ==

The '''second problem''' is that originally, the default for Manage > Users was to list all 6000+ users on one page, which lead to long delays. The default should be to show the first 25 users and there should be options to list 100, 250, or all users.

'''Purpose:'''
The reason behind adding this feature is also to make it the list of users easier to read, possibly reduce retrieval and loading time, and improve ease of navigation.

== Solution 2 ==

[[File:Img3_1743_new.jpg|center|Solution for division and navigation of pages]]

The yellow portion in the above screenshot is where we have added options to display 25, 100, 250, or all users at once, along with links to ‘previous’ and ‘next’ pages.

'''Changes:'''

There is a gem called will_paginate that adds a pagination library which integrates with ruby on rails. That gem is already added to the gemfile of expertiza, but was not used in this particular page. Once added, it provides a paginate method which automatically generates a paginated list with a per_page parameter. Then that list is passed to the view, which automatically displays the necessary links such as “previous”, “next”, individual page links, etc

Here's what the code originally looked like:

[[File:Img5_1743.jpg|center|Original code for user.rb]]

Here's what we have changed that to:

[[File:Img6_1743.png|center|New code for user.rb]]

== Implementation ==
The following files have been modified:

Models:

- user.rb

Controllers:

- users_controller.rb

Views:

- users/list.html.erb

- assignments/list_submissions.html.erb

- grades/view.html.erb

- review_mapping/response_report.html.haml

- assessment360/all_students_all_reviews.html.erb

== Test Plan ==

Most of the testing for this project is fairly simple.

'''Manual:'''

Problem 1:
All of the altered links will need to be tested to ensure they link to the correct pages. Tests that check if the username link correctly initiates impersonation of that user, and that clicking the full name links to the right user profile.

A test user needs to be created and the email link will be used to ensure emails are correctly sent.

Problem 2:
For the second part of the project, tests need to be set up to check that the correct number of students are being displayed for each display option, and that the user can display subsequent pages of users.

'''Automated:'''

Problem 1 includes changes in view files. Hence, we are not planning to create automated test cases for problem 1.

Problem 2:
Unit Tests: We will add unit test cases in user_spec.rb.
Case I:
Condition: page number = 4 and per page option = 25
Result: Ensure users list contain 25 entries.
Case II:
Condition: page number = 1 and per page option = 50
Result: Ensure users list contain all entries.

CSC/ECE 517 Spring 2017/E1743

2017-05-08T00:02:58Z

Fsmisarw:

== Problem Statement 1 ==

Expertiza has a feature that allows instructor i (or an admin) to impersonate a user whose account was created by i or recursively by a user that i created. This causes Expertiza to show what the impersonated user would see. It is good for tracking down bugs in what students see and also for accessing functionality that cannot be accessed from, or is too slow to access from, the instructor UI. Impersonating is currently performed by going to the pull-down menu at the top of the window and selecting Manage > Impersonate user. However, usually the instructor initiates impersonation after finding the student in some kind of list, like a list of users, or assignment participants, or as a member of a team signed up for a topic, etc. In this case, it is inconvenient to have to go to the pulldown menu and type in the user ID. It would be better if the instructor could just click on the ID in the list, and immediately have the impersonated user’s homepage show up.

Here’s what it looks like:

[[File:Img1_1743.JPG|center|Screenshot of the current Impersonate User page]]

The idea is to have more convenient options for instructors where a list of students is available, making it easier to both impersonate and view the details of any student with direct links.

== Solution 1 ==

[[File:Img2_1743_new.jpg|center|Solution for Impersonate User links]]

We have made the following changes to the system as shown by the screenshot above.

Red: The student ID previously had a link that directs to the user profile page. We have changed that to a link that would impersonate the user immediately. We did this by calling the impersonate function directly from this page and passing the user's ID as a parameter.

Blue: The user profile page link was shifted to this column instead. This column originally did not have any link on it.

Green: A link on the email address which now invokes a mailto: HTML link. This column also previously did not have any links.

The following screens did not previously show the user-ID, but we have modified them to do so.

- View scores (User IDs could be shown below names in the Contributor column.)

- View review report

- Author feedback report (available from the pull-down menu on Review report).

- Teammate review report ( “ “ “)

All these pages display some part of the user model, meaning they have all the data from the model. So, it was just a matter of displaying the appropriate user-ID.

'''Changes:'''

The changes we made on this part are the addition of lines printing the user-ID, and it was presented with a link which calls the impersonate function, using the user's ID as a parameter. The following snippet of code shows the exact lines we have changed.

[[File:Img4_1743.jpg|center|Code for Impersonate User links]]

== Problem Statement 2 ==

The '''second problem''' is that originally, the default for Manage > Users was to list all 6000+ users on one page, which lead to long delays. The default should be to show the first 25 users and there should be options to list 100, 250, or all users.

'''Purpose:'''
The reason behind adding this feature is also to make it the list of users easier to read, possibly reduce retrieval and loading time, and improve ease of navigation.

== Solution 2 ==

[[File:Img3_1743_new.jpg|center|Solution for division and navigation of pages]]

The yellow portion in the above screenshot is where we have added options to display 25, 100, 250, or all users at once, along with links to ‘previous’ and ‘next’ pages.

'''Changes:'''

There is a gem called will_paginate that adds a pagination library which integrates with ruby on rails. That gem is already added to the gemfile of expertiza, but was not used in this particular page. Once added, it provides a paginate method which automatically generates a paginated list with a per_page parameter. Then that list is passed to the view, which automatically displays the necessary links such as “previous”, “next”, individual page links, etc

Here's what the code originally looked like:

[[File:Img5_1743.jpg|center|Original code for user.rb]]

Here's what we have changed that to:

[[File:Img6_1743.jpg|center|New code for user.rb]]

== Implementation ==
The following files have been modified:

Models:

- user.rb

Controllers:

- users_controller.rb

Views:

- users/list.html.erb

- assignments/list_submissions.html.erb

- grades/view.html.erb

- review_mapping/response_report.html.haml

- assessment360/all_students_all_reviews.html.erb

== Test Plan ==

Most of the testing for this project is fairly simple.

'''Manual:'''

Problem 1:
All of the altered links will need to be tested to ensure they link to the correct pages. Tests that check if the username link correctly initiates impersonation of that user, and that clicking the full name links to the right user profile.

A test user needs to be created and the email link will be used to ensure emails are correctly sent.

Problem 2:
For the second part of the project, tests need to be set up to check that the correct number of students are being displayed for each display option, and that the user can display subsequent pages of users.

'''Automated:'''

Problem 1 includes changes in view files. Hence, we are not planning to create automated test cases for problem 1.

Problem 2:
Unit Tests: We will add unit test cases in user_spec.rb.
Case I:
Condition: page number = 4 and per page option = 25
Result: Ensure users list contain 25 entries.
Case II:
Condition: page number = 1 and per page option = 50
Result: Ensure users list contain all entries.

File:Img6 1743.png

2017-05-08T00:00:44Z

Fsmisarw:

File:Img5 1743.jpg

2017-05-08T00:00:36Z

Fsmisarw:

CSC/ECE 517 Spring 2017/E1743

2017-05-07T23:54:09Z

Fsmisarw:

== Problem Statement 1 ==

Expertiza has a feature that allows instructor i (or an admin) to impersonate a user whose account was created by i or recursively by a user that i created. This causes Expertiza to show what the impersonated user would see. It is good for tracking down bugs in what students see and also for accessing functionality that cannot be accessed from, or is too slow to access from, the instructor UI. Impersonating is currently performed by going to the pull-down menu at the top of the window and selecting Manage > Impersonate user. However, usually the instructor initiates impersonation after finding the student in some kind of list, like a list of users, or assignment participants, or as a member of a team signed up for a topic, etc. In this case, it is inconvenient to have to go to the pulldown menu and type in the user ID. It would be better if the instructor could just click on the ID in the list, and immediately have the impersonated user’s homepage show up.

Here’s what it looks like:

[[File:Img1_1743.JPG|center|Screenshot of the current Impersonate User page]]

The idea is to have more convenient options for instructors where a list of students is available, making it easier to both impersonate and view the details of any student with direct links.

== Solution 1 ==

[[File:Img2_1743_new.jpg|center|Solution for Impersonate User links]]

We have made the following changes to the system as shown by the screenshot above.

Red: The student ID previously had a link that directs to the user profile page. We have changed that to a link that would impersonate the user immediately. We did this by calling the impersonate function directly from this page and passing the user's ID as a parameter.

Blue: The user profile page link was shifted to this column instead. This column originally did not have any link on it.

Green: A link on the email address which now invokes a mailto: HTML link. This column also previously did not have any links.

The following screens did not previously show the user-ID, but we have modified them to do so.

- View scores (User IDs could be shown below names in the Contributor column.)

- View review report

- Author feedback report (available from the pull-down menu on Review report).

- Teammate review report ( “ “ “)

All these pages display some part of the user model, meaning they have all the data from the model. So, it was just a matter of displaying the appropriate user-ID.

'''Changes:'''

The changes we made on this part are the addition of lines printing the user-ID, and it was presented with a link which calls the impersonate function, using the user's ID as a parameter. The following snippet of code shows the exact lines we have changed.

[[File:Img4_1743.jpg|center|Code for Impersonate User links]]

== Problem Statement 2 ==

The '''second problem''' is that originally, the default for Manage > Users was to list all 6000+ users on one page, which lead to long delays. The default should be to show the first 25 users and there should be options to list 100, 250, or all users.

'''Purpose:'''
The reason behind adding this feature is also to make it the list of users easier to read, possibly reduce retrieval and loading time, and improve ease of navigation.

== Solution 2 ==

[[File:Img3_1743_new.jpg|center|Solution for division and navigation of pages]]

The yellow portion in the above screenshot is where we have added options to display 25, 100, 250, or all users at once, along with links to ‘previous’ and ‘next’ pages.

'''Changes:'''

There is a gem called will_paginate that adds a pagination library which integrates with ruby on rails. That gem is already added to the gemfile of expertiza, but was not used in this particular page. Once added, it provides a paginate method which automatically generates a paginated list with a per_page parameter. Then that list is passed to the view, which automatically displays the necessary links such as “previous”, “next”, individual page links, etc

== Implementation ==
The following files have been modified:

Models:

- user.rb

Controllers:

- users_controller.rb

Views:

- users/list.html.erb

- assignments/list_submissions.html.erb

- grades/view.html.erb

- review_mapping/response_report.html.haml

- assessment360/all_students_all_reviews.html.erb

== Test Plan ==

Most of the testing for this project is fairly simple.

'''Manual:'''

Problem 1:
All of the altered links will need to be tested to ensure they link to the correct pages. Tests that check if the username link correctly initiates impersonation of that user, and that clicking the full name links to the right user profile.

A test user needs to be created and the email link will be used to ensure emails are correctly sent.

Problem 2:
For the second part of the project, tests need to be set up to check that the correct number of students are being displayed for each display option, and that the user can display subsequent pages of users.

'''Automated:'''

Problem 1 includes changes in view files. Hence, we are not planning to create automated test cases for problem 1.

Problem 2:
Unit Tests: We will add unit test cases in user_spec.rb.
Case I:
Condition: page number = 4 and per page option = 25
Result: Ensure users list contain 25 entries.
Case II:
Condition: page number = 1 and per page option = 50
Result: Ensure users list contain all entries.

File:Img4 1743.jpg

2017-05-07T23:53:11Z

Fsmisarw:

CSC/ECE 517 Spring 2017/E1743

2017-05-07T23:52:58Z

Fsmisarw:

== Problem Statement 1 ==

Expertiza has a feature that allows instructor i (or an admin) to impersonate a user whose account was created by i or recursively by a user that i created. This causes Expertiza to show what the impersonated user would see. It is good for tracking down bugs in what students see and also for accessing functionality that cannot be accessed from, or is too slow to access from, the instructor UI. Impersonating is currently performed by going to the pull-down menu at the top of the window and selecting Manage > Impersonate user. However, usually the instructor initiates impersonation after finding the student in some kind of list, like a list of users, or assignment participants, or as a member of a team signed up for a topic, etc. In this case, it is inconvenient to have to go to the pulldown menu and type in the user ID. It would be better if the instructor could just click on the ID in the list, and immediately have the impersonated user’s homepage show up.

Here’s what it looks like:

[[File:Img1_1743.JPG|center|Screenshot of the current Impersonate User page]]

The idea is to have more convenient options for instructors where a list of students is available, making it easier to both impersonate and view the details of any student with direct links.

== Solution 1 ==

[[File:Img2_1743_new.jpg|center|Solution for Impersonate User links]]

We have made the following changes to the system as shown by the screenshot above.

Red: The student ID previously had a link that directs to the user profile page. We have changed that to a link that would impersonate the user immediately. We did this by calling the impersonate function directly from this page and passing the user's ID as a parameter.

Blue: The user profile page link was shifted to this column instead. This column originally did not have any link on it.

Green: A link on the email address which now invokes a mailto: HTML link. This column also previously did not have any links.

The following screens did not previously show the user-ID, but we have modified them to do so.

- View scores (User IDs could be shown below names in the Contributor column.)

- View review report

- Author feedback report (available from the pull-down menu on Review report).

- Teammate review report ( “ “ “)

All these pages display some part of the user model, meaning they have all the data from the model. So, it was just a matter of displaying the appropriate user-ID.

'''Changes:'''

The changes we made on this part are the addition of lines printing the user-ID, and it was presented with a link which calls the impersonate function, using the user's ID as a parameter. The following snippet of code shows the exact lines we have changed.

[[File:Img4_1743_new.jpg|center|Code for Impersonate User links]]

== Problem Statement 2 ==

The '''second problem''' is that originally, the default for Manage > Users was to list all 6000+ users on one page, which lead to long delays. The default should be to show the first 25 users and there should be options to list 100, 250, or all users.

'''Purpose:'''
The reason behind adding this feature is also to make it the list of users easier to read, possibly reduce retrieval and loading time, and improve ease of navigation.

== Solution 2 ==

[[File:Img3_1743_new.jpg|center|Solution for division and navigation of pages]]

The yellow portion in the above screenshot is where we have added options to display 25, 100, 250, or all users at once, along with links to ‘previous’ and ‘next’ pages.

'''Changes:'''

There is a gem called will_paginate that adds a pagination library which integrates with ruby on rails. That gem is already added to the gemfile of expertiza, but was not used in this particular page. Once added, it provides a paginate method which automatically generates a paginated list with a per_page parameter. Then that list is passed to the view, which automatically displays the necessary links such as “previous”, “next”, individual page links, etc

== Implementation ==
The following files have been modified:

Models:

- user.rb

Controllers:

- users_controller.rb

Views:

- users/list.html.erb

- assignments/list_submissions.html.erb

- grades/view.html.erb

- review_mapping/response_report.html.haml

- assessment360/all_students_all_reviews.html.erb

== Test Plan ==

Most of the testing for this project is fairly simple.

'''Manual:'''

Problem 1:
All of the altered links will need to be tested to ensure they link to the correct pages. Tests that check if the username link correctly initiates impersonation of that user, and that clicking the full name links to the right user profile.

A test user needs to be created and the email link will be used to ensure emails are correctly sent.

Problem 2:
For the second part of the project, tests need to be set up to check that the correct number of students are being displayed for each display option, and that the user can display subsequent pages of users.

'''Automated:'''

Problem 1 includes changes in view files. Hence, we are not planning to create automated test cases for problem 1.

Problem 2:
Unit Tests: We will add unit test cases in user_spec.rb.
Case I:
Condition: page number = 4 and per page option = 25
Result: Ensure users list contain 25 entries.
Case II:
Condition: page number = 1 and per page option = 50
Result: Ensure users list contain all entries.

CSC/ECE 517 Spring 2017/E1743

2017-05-07T23:18:51Z

Fsmisarw:

== Problem Statement 1 ==

Expertiza has a feature that allows instructor i (or an admin) to impersonate a user whose account was created by i or recursively by a user that i created. This causes Expertiza to show what the impersonated user would see. It is good for tracking down bugs in what students see and also for accessing functionality that cannot be accessed from, or is too slow to access from, the instructor UI. Impersonating is currently performed by going to the pull-down menu at the top of the window and selecting Manage > Impersonate user. However, usually the instructor initiates impersonation after finding the student in some kind of list, like a list of users, or assignment participants, or as a member of a team signed up for a topic, etc. In this case, it is inconvenient to have to go to the pulldown menu and type in the user ID. It would be better if the instructor could just click on the ID in the list, and immediately have the impersonated user’s homepage show up.

Here’s what it looks like:

[[File:Img1_1743.JPG|center|Screenshot of the current Impersonate User page]]

The idea is to have more convenient options for instructors where a list of students is available, making it easier to both impersonate and view the details of any student with direct links.

== Solution 1 ==

[[File:Img2_1743_new.jpg|center|Solution for Impersonate User links]]

We have made the following changes to the system as shown by the screenshot above.

Red: The student ID previously had a link that directs to the user profile page. We have changed that to a link that would impersonate the user immediately. We did this by calling the impersonate function directly from this page and passing the user's ID as a parameter.

Blue: The user profile page link was shifted to this column instead. This column originally did not have any link on it.

Green: A link on the email address which now invokes a mailto: HTML link. This column also previously did not have any links.

The following screens did not previously show the user-ID, but we have modified them to do so.

- View scores (User IDs could be shown below names in the Contributor column.)

- View review report

- Author feedback report (available from the pull-down menu on Review report).

- Teammate review report ( “ “ “)

All these pages display some part of the user model, meaning they have all the data from the model. So, it was just a matter of displaying the appropriate user-ID.

'''Changes:'''

The changes we made on this part are the addition of lines printing the user-ID, and it was presented with a link which calls the impersonate function, using the user's ID as a parameter.

== Problem Statement 2 ==

The '''second problem''' is that originally, the default for Manage > Users was to list all 6000+ users on one page, which lead to long delays. The default should be to show the first 25 users and there should be options to list 100, 250, or all users.

'''Purpose:'''
The reason behind adding this feature is also to make it the list of users easier to read, possibly reduce retrieval and loading time, and improve ease of navigation.

== Solution 2 ==

[[File:Img3_1743_new.jpg|center|Solution for division and navigation of pages]]

The yellow portion in the above screenshot is where we have added options to display 25, 100, 250, or all users at once, along with links to ‘previous’ and ‘next’ pages.

'''Changes:'''

There is a gem called will_paginate that adds a pagination library which integrates with ruby on rails. That gem is already added to the gemfile of expertiza, but was not used in this particular page. Once added, it provides a paginate method which automatically generates a paginated list with a per_page parameter. Then that list is passed to the view, which automatically displays the necessary links such as “previous”, “next”, individual page links, etc

== Implementation ==
The following files have been modified:

Models:

- user.rb

Controllers:

- users_controller.rb

Views:

- users/list.html.erb

- assignments/list_submissions.html.erb

- grades/view.html.erb

- review_mapping/response_report.html.haml

- assessment360/all_students_all_reviews.html.erb

== Test Plan ==

Most of the testing for this project is fairly simple.

'''Manual:'''

Problem 1:
All of the altered links will need to be tested to ensure they link to the correct pages. Tests that check if the username link correctly initiates impersonation of that user, and that clicking the full name links to the right user profile.

A test user needs to be created and the email link will be used to ensure emails are correctly sent.

Problem 2:
For the second part of the project, tests need to be set up to check that the correct number of students are being displayed for each display option, and that the user can display subsequent pages of users.

'''Automated:'''

Problem 1 includes changes in view files. Hence, we are not planning to create automated test cases for problem 1.

Problem 2:
Unit Tests: We will add unit test cases in user_spec.rb.
Case I:
Condition: page number = 4 and per page option = 25
Result: Ensure users list contain 25 entries.
Case II:
Condition: page number = 1 and per page option = 50
Result: Ensure users list contain all entries.

File:Img3 1743 new.jpg

2017-05-07T23:17:40Z

Fsmisarw:

File:Img2 1743 new.jpg

2017-05-07T23:17:15Z

Fsmisarw:

CSC/ECE 517 Spring 2017/E1743

2017-05-07T23:16:22Z

Fsmisarw:

== Problem Statement 1 ==

Expertiza has a feature that allows instructor i (or an admin) to impersonate a user whose account was created by i or recursively by a user that i created. This causes Expertiza to show what the impersonated user would see. It is good for tracking down bugs in what students see and also for accessing functionality that cannot be accessed from, or is too slow to access from, the instructor UI. Impersonating is currently performed by going to the pull-down menu at the top of the window and selecting Manage > Impersonate user. However, usually the instructor initiates impersonation after finding the student in some kind of list, like a list of users, or assignment participants, or as a member of a team signed up for a topic, etc. In this case, it is inconvenient to have to go to the pulldown menu and type in the user ID. It would be better if the instructor could just click on the ID in the list, and immediately have the impersonated user’s homepage show up.

Here’s what it looks like:

[[File:Img1_1743.JPG|center|Screenshot of the current Impersonate User page]]

The idea is to have more convenient options for instructors where a list of students is available, making it easier to both impersonate and view the details of any student with direct links.

== Solution 1 ==

[[File:Img2_1743.JPG|center|Solution for Impersonate User links]]

We have made the following changes to the system as shown by the screenshot above.

Red: The student ID previously had a link that directs to the user profile page. We have changed that to a link that would impersonate the user immediately. We did this by calling the impersonate function directly from this page and passing the user's ID as a parameter.

Blue: The user profile page link was shifted to this column instead. This column originally did not have any link on it.

Green: A link on the email address which now invokes a mailto: HTML link. This column also previously did not have any links.

The following screens did not previously show the user-ID, but we have modified them to do so.

- View scores (User IDs could be shown below names in the Contributor column.)

- View review report

- Author feedback report (available from the pull-down menu on Review report).

- Teammate review report ( “ “ “)

All these pages display some part of the user model, meaning they have all the data from the model. So, it was just a matter of displaying the appropriate user-ID.

'''Changes:'''

The changes we made on this part are the addition of lines printing the user-ID, and it was presented with a link which calls the impersonate function, using the user's ID as a parameter.

== Problem Statement 2 ==

The '''second problem''' is that originally, the default for Manage > Users was to list all 6000+ users on one page, which lead to long delays. The default should be to show the first 25 users and there should be options to list 100, 250, or all users.

'''Purpose:'''
The reason behind adding this feature is also to make it the list of users easier to read, possibly reduce retrieval and loading time, and improve ease of navigation.

== Solution 2 ==

[[File:Img3_1743.JPG|center|Solution for division and navigation of pages]]

The yellow portion in the above screenshot is where we have added options to display 25, 100, 250, or all users at once, along with links to ‘previous’ and ‘next’ pages.

'''Changes:'''

There is a gem called will_paginate that adds a pagination library which integrates with ruby on rails. That gem is already added to the gemfile of expertiza, but was not used in this particular page. Once added, it provides a paginate method which automatically generates a paginated list with a per_page parameter. Then that list is passed to the view, which automatically displays the necessary links such as “previous”, “next”, individual page links, etc

== Implementation ==
The following files have been modified:

Models:

- user.rb

Controllers:

- users_controller.rb

Views:

- users/list.html.erb

- assignments/list_submissions.html.erb

- grades/view.html.erb

- review_mapping/response_report.html.haml

- assessment360/all_students_all_reviews.html.erb

== Test Plan ==

Most of the testing for this project is fairly simple.

'''Manual:'''

Problem 1:
All of the altered links will need to be tested to ensure they link to the correct pages. Tests that check if the username link correctly initiates impersonation of that user, and that clicking the full name links to the right user profile.

A test user needs to be created and the email link will be used to ensure emails are correctly sent.

Problem 2:
For the second part of the project, tests need to be set up to check that the correct number of students are being displayed for each display option, and that the user can display subsequent pages of users.

'''Automated:'''

Problem 1 includes changes in view files. Hence, we are not planning to create automated test cases for problem 1.

Problem 2:
Unit Tests: We will add unit test cases in user_spec.rb.
Case I:
Condition: page number = 4 and per page option = 25
Result: Ensure users list contain 25 entries.
Case II:
Condition: page number = 1 and per page option = 50
Result: Ensure users list contain all entries.

File:Img3 1743.jpg

2017-05-07T23:15:28Z

Fsmisarw: uploaded a new version of "File:Img3 1743.jpg"

File:Img2 1743.jpg

2017-05-07T23:15:06Z

Fsmisarw: uploaded a new version of "File:Img2 1743.jpg"

File:Img3 1743.jpg

2017-05-07T23:14:00Z

Fsmisarw:

File:Img2 1743.jpg

2017-05-07T23:13:43Z

Fsmisarw:

CSC/ECE 517 Spring 2017/E1743

2017-05-07T22:50:21Z

Fsmisarw:

== Problem Statement 1 ==

Expertiza has a feature that allows instructor i (or an admin) to impersonate a user whose account was created by i or recursively by a user that i created. This causes Expertiza to show what the impersonated user would see. It is good for tracking down bugs in what students see and also for accessing functionality that cannot be accessed from, or is too slow to access from, the instructor UI. Impersonating is currently performed by going to the pull-down menu at the top of the window and selecting Manage > Impersonate user. However, usually the instructor initiates impersonation after finding the student in some kind of list, like a list of users, or assignment participants, or as a member of a team signed up for a topic, etc. In this case, it is inconvenient to have to go to the pulldown menu and type in the user ID. It would be better if the instructor could just click on the ID in the list, and immediately have the impersonated user’s homepage show up.

Here’s what it looks like:

[[File:Img1_1743.JPG|center|Screenshot of the current Impersonate User page]]

The idea is to have more convenient options for instructors where a list of students is available, making it easier to both impersonate and view the details of any student with direct links.

== Solution 1 ==

[[File:Img2_1743.JPG|center|Proposal for Impersonate User links]]

We have made the following changes to the system as shown by the screenshot above.

Red: The student ID previously had a link that directs to the user profile page. We have changed that to a link that would impersonate the user immediately. We did this by calling the impersonate function directly from this page and passing the user's ID as a parameter.

Blue: The user profile page link was shifted to this column instead. This column originally did not have any link on it.

Green: A link on the email address which now invokes a mailto: HTML link. This column also previously did not have any links.

The following screens did not previously show the user-ID, but we have modified them to do so.

- View scores (User IDs could be shown below names in the Contributor column.)

- View review report

- Author feedback report (available from the pull-down menu on Review report).

- Teammate review report ( “ “ “)

All these pages display some part of the user model, meaning they have all the data from the model. So, it was just a matter of displaying the appropriate user-ID.

'''Changes:'''

The changes we made on this part are the addition of lines printing the user-ID, and it was presented with a link which calls the impersonate function, using the user's ID as a parameter.

== Problem Statement 2 ==

The '''second problem''' is that originally, the default for Manage > Users was to list all 6000+ users on one page, which lead to long delays. The default should be to show the first 25 users and there should be options to list 100, 250, or all users.

'''Purpose:'''
The reason behind adding this feature is also to make it the list of users easier to read, possibly reduce retrieval and loading time, and improve ease of navigation.

== Solution 2 ==

[[File:Img3_1743.JPG|center|Proposal for division and navigation of pages]]

The yellow portion in the above screenshot is where we have added options to display 25, 100, 250, or all users at once, along with links to ‘previous’ and ‘next’ pages.

'''Changes:'''

There is a gem called will_paginate that adds a pagination library which integrates with ruby on rails. That gem is already added to the gemfile of expertiza, but was not used in this particular page. Once added, it provides a paginate method which automatically generates a paginated list with a per_page parameter. Then that list is passed to the view, which automatically displays the necessary links such as “previous”, “next”, individual page links, etc

== Implementation ==
The following files have been modified:

Models:

- user.rb

Controllers:

- users_controller.rb

Views:

- users/list.html.erb

- assignments/list_submissions.html.erb

- grades/view.html.erb

- review_mapping/response_report.html.haml

- assessment360/all_students_all_reviews.html.erb

== Test Plan ==

Most of the testing for this project is fairly simple.

'''Manual:'''

Problem 1:
All of the altered links will need to be tested to ensure they link to the correct pages. Tests that check if the username link correctly initiates impersonation of that user, and that clicking the full name links to the right user profile.

A test user needs to be created and the email link will be used to ensure emails are correctly sent.

Problem 2:
For the second part of the project, tests need to be set up to check that the correct number of students are being displayed for each display option, and that the user can display subsequent pages of users.

'''Automated:'''

Problem 1 includes changes in view files. Hence, we are not planning to create automated test cases for problem 1.

Problem 2:
Unit Tests: We will add unit test cases in user_spec.rb.
Case I:
Condition: page number = 4 and per page option = 25
Result: Ensure users list contain 25 entries.
Case II:
Condition: page number = 1 and per page option = 50
Result: Ensure users list contain all entries.

CSC/ECE 517 Spring 2017/E1743

2017-05-07T22:40:21Z

Fsmisarw:

== Problem Statement 1 ==

Expertiza has a feature that allows instructor i (or an admin) to impersonate a user whose account was created by i or recursively by a user that i created. This causes Expertiza to show what the impersonated user would see. It is good for tracking down bugs in what students see and also for accessing functionality that cannot be accessed from, or is too slow to access from, the instructor UI. Impersonating is currently performed by going to the pull-down menu at the top of the window and selecting Manage > Impersonate user. However, usually the instructor initiates impersonation after finding the student in some kind of list, like a list of users, or assignment participants, or as a member of a team signed up for a topic, etc. In this case, it is inconvenient to have to go to the pulldown menu and type in the user ID. It would be better if the instructor could just click on the ID in the list, and immediately have the impersonated user’s homepage show up.

Here’s what it currently looks like:

[[File:Img1_1743.JPG|center|Screenshot of the current Impersonate User page]]

The idea is to have more convenient options for instructors where a list of students is available, making it easier to both impersonate and view the details of any student with direct links.

== Solution 1 ==

[[File:Img2_1743.JPG|center|Proposal for Impersonate User links]]

We have made the following changes to the system as shown by the screenshot above.

Red: The student ID previously had a link that directs to the user profile page. We have changed that to a link that would impersonate the user immediately. We did this by calling the impersonate function directly from this page and passing the user's ID as a parameter.

Blue: The user profile page link was shifted to this column instead. This column originally did not have any link on it.

Green: A link on the email address which now invokes a mailto: HTML link. This column also previously did not have any links.

The following screens did not previously show the user-ID, but we have modified them to do so.

- View scores (User IDs could be shown below names in the Contributor column.)

- View review report

- Author feedback report (available from the pulldown menu on Review report).

- Teammate review report ( “ “ “)

All these pages display some part of the user model, meaning they have all the data from the model. So, it wass just a matter of displaying the appropriate user-ID.

== Problem Statement 2 ==

The '''second problem''' is that currently the default for Manage > Users is to list all 6000+ users on one page, which leads to long delays. The default should be to show the first 25 users and there should be options to list 100, 250, or all users.

'''Purpose:'''
The reason behind adding this feature is also to make it the list of users easier to read, possibly reduce retrieval and loading time, and improve ease of navigation.

== Solution 2 ==

[[File:Img3_1743.JPG|center|Proposal for division and navigation of pages]]

The yellow portion in the above screenshot is where we have added options to display 25, 100, 250, or all users at once, along with links to ‘previous’ and ‘next’ pages.

'''Changes:'''

There is a gem called will_paginate that adds a pagination library which integrates with ruby on rails. That gem is already added to the gemfile of expertiza, but was not used in this particular page. Once added, it provides a paginate method which automatically generates a paginated list with a per_page parameter. Then that list is passed to the view, which automatically displays the necessary links such as “previous”, “next”, individual page links, etc

== Implementation ==
The following files have been modified:

Models:

- user.rb

Controllers:

- users_controller.rb

Views:

- users/list.html.erb

- assignments/list_submissions.html.erb

- grades/view.html.erb

- review_mapping/response_report.html.haml

- assessment360/all_students_all_reviews.html.erb

== Test Plan ==

Most of the testing for this project is fairly simple.

'''Manual:'''

Problem 1:
All of the altered links will need to be tested to ensure they link to the correct pages. Tests that check if the username link correctly initiates impersonation of that user, and that clicking the full name links to the right user profile.

A test user needs to be created and the email link will be used to ensure emails are correctly sent.

Problem 2:
For the second part of the project, tests need to be set up to check that the correct number of students are being displayed for each display option, and that the user can display subsequent pages of users.

'''Automated:'''

Problem 1 includes changes in view files. Hence, we are not planning to create automated test cases for problem 1.

Problem 2:
Unit Tests: We will add unit test cases in user_spec.rb.
Case I:
Condition: page number = 4 and per page option = 25
Result: Ensure users list contain 25 entries.
Case II:
Condition: page number = 1 and per page option = 50
Result: Ensure users list contain all entries.

CSC/ECE 517 Spring 2017/E1743

2017-04-13T01:25:03Z

Fsmisarw:

== Problem Statement 1 ==

Expertiza has a feature that allows instructor i (or an admin) to impersonate a user whose account was created by i or recursively by a user that i created. This causes Expertiza to show what the impersonated user would see. It is good for tracking down bugs in what students see and also for accessing functionality that cannot be accessed from, or is too slow to access from, the instructor UI. Impersonating is currently performed by going to the pull-down menu at the top of the window and selecting Manage > Impersonate user. However, usually the instructor initiates impersonation after finding the student in some kind of list, like a list of users, or assignment participants, or as a member of a team signed up for a topic, etc. In this case, it is inconvenient to have to go to the pulldown menu and type in the user ID. It would be better if the instructor could just click on the ID in the list, and immediately have the impersonated user’s homepage show up.

Here’s what it currently looks like:

[[File:Img1_1743.JPG|center|Screenshot of the current Impersonate User page]]

The idea is to have more convenient options for instructors where a list of students is available, making it easier to both impersonate and view the details of any student with direct links.

== Proposal 1 ==

[[File:Img2_1743.JPG|center|Proposal for Impersonate User links]]

Red: The student ID currently has a link that directs to the user profile page. We intend to change that to a link that would impersonate the user.

Blue: The user profile page link would be shifted to this column instead.

Green: A link on the email address which would invoke a mailto: HTML link.

The following screens do not currently show the user-ID, but we intend to modify them to do so.

- View scores (User IDs could be shown below names in the Contributor column.)

- View review report

- Author feedback report (available from the pulldown menu on Review report).

- Teammate review report ( “ “ “)

'''Tentative Changes'''

Red: The student ID currently has a link that directs to the user profile page. We intend to change that to a link that would impersonate the user. This would be done by bypassing the separate impersonate page. The only parameter required for impersonating a person is his user-ID. Since we have a list of users with their ID here, it would be easy to skip the view where the ID is entered, and move to the next link.

Blue: The user profile page link would be shifted to this link instead.

Green: A link on the email address which would invoke a mailto: HTML link.

The following screens do not currently show the user-ID, but we intend to modify them to do so, and add click to impersonate to them.

- View scores

- View review report

- Author feedback report

- Teammate review report

All these pages display some part of the user model, meaning they have all the data from the model. So, it is just a matter of displaying the appropriate user-ID.

== Problem Statement 2 ==

The '''second problem''' is that currently the default for Manage > Users is to list all 6000+ users on one page, which leads to long delays. The default should be to show the first 25 users and there should be options to list 100, 250, or all users.

'''Purpose:'''
The reason behind adding this feature is also to make it the list of users easier to read, possibly reduce retrieval and loading time, and improve ease of navigation.

== Proposal 2 ==

[[File:Img3_1743.JPG|center|Proposal for division and navigation of pages]]

The yellow portion in the above screenshot is space we can use to add options to display 25, 100, 250, or all users at once, along with links to ‘previous’ and ‘next’ pages.

'''Tentative Changes:'''

There is a gem called will_paginate that adds a pagination library which integrates with ruby on rails. That gem is already added to the gemfile of expertiza, but is not used in this particular page. Once added, it provides a paginate method which automatically generates a paginated list with a per_page parameter. Then that list can be passed to the view, which automatically displays the necessary links such as “previous”, “next”, individual page links, etc

== Implementation ==
The following files will most likely be modified:

Models:

- user.rb

Controllers:

- users_controller.rb

Views:

- users/list.html.erb

- assignments/list_submissions.html.erb

- grades/view.html.erb

- review_mapping/response_report.html.haml

- assessment360/all_students_all_reviews.html.erb

== Test Plan ==

Most of the testing for this project will be fairly simple.

'''Manual:'''

Problem 1:
All of the altered links will need to be tested to ensure they link to the correct pages. Tests that check if the username link correctly initiates impersonation of that user, and that clicking the full name links to the right user profile.

A test user needs to be created and the email link will be used to ensure emails are correctly sent.

Problem 2:
For the second part of the project, tests need to be set up to check that the correct number of students are being displayed for each display option, and that the user can display subsequent pages of users.

'''Automated:'''

Problem 1 includes changes in view files. Hence, we are not planning to create automated test cases for problem 1.

Problem 2:
Unit Tests: We will add unit test cases in user_spec.rb.
Case I:
Condition: page number = 4 and per page option = 25
Result: Ensure users list contain 25 entries.
Case II:
Condition: page number = 1 and per page option = 50
Result: Ensure users list contain all entries.

CSC/ECE 517 Spring 2017/E1743

2017-04-12T22:02:26Z

Fsmisarw:

CSC/ECE 517 Spring 2017/E1743

2017-04-12T22:02:01Z

Fsmisarw:

CSC/ECE 517 Spring 2017/E1743

2017-04-12T21:48:28Z

Fsmisarw:

CSC/ECE 517 Spring 2017/E1743

2017-04-12T21:47:15Z

Fsmisarw:

File:Img3 1743.JPG

2017-04-12T21:46:46Z

Fsmisarw:

File:17431.jpg

2017-04-12T21:45:25Z

Fsmisarw:

File:Img3. 1743.JPG

2017-04-12T21:43:40Z

Fsmisarw:

File:Img2 1743.JPG

2017-04-12T21:43:02Z

Fsmisarw:

File:Img1 1743.JPG

2017-04-12T21:42:09Z

Fsmisarw: new screenshot

new screenshot

CSC/ECE 517 Spring 2017/E1743

2017-04-12T21:41:18Z

Fsmisarw:

CSC/ECE 517 Spring 2017/E1743

2017-04-12T21:34:46Z

Fsmisarw:

'''Problem:'''

Expertiza has a feature that allows instructor i (or an admin) to impersonate a user whose account was created by i or recursively by a user that i created. This causes Expertiza to show what the impersonated user would see. It is good for tracking down bugs in what students see and also for accessing functionality that cannot be accessed from, or is too slow to access from, the instructor UI. Impersonating is currently performed by going to the pull-down menu at the top of the window and selecting Manage > Impersonate user. However, usually the instructor initiates impersonation after finding the student in some kind of list, like a list of users, or assignment participants, or as a member of a team signed up for a topic, etc. In this case, it is inconvenient to have to go to the pulldown menu and type in the user ID. It would be better if the instructor could just click on the ID in the list, and immediately have the impersonated user’s homepage show up.

Here’s what it currently looks like:

[[File:Img1.jpg|center|Screenshot of the current Impersonate User page]]

'''Why''' we are working on the above stated problem:
The idea is to have more convenient options for instructors where a list of students is available, making it easier to both impersonate and view the details of any student with direct links.

[[File:Img2.jpg|center|Proposal for Impersonate User links]]

'''Proposal:'''
Red: The student ID currently has a link that directs to the user profile page. We intend to change that to a link that would impersonate the user.
Blue: The user profile page link would be shifted to this column instead.
Green: A link on the email address which would invoke a mailto: HTML link.

The following screens do not currently show the user-ID, but we intend to modify them to do so.
View scores (User IDs could be shown below names in the Contributor column.)
View review report
Author feedback report (available from the pulldown menu on Review report).
Teammate review report ( “ “ “)

The '''second problem''' is that currently the default for Manage > Users is to list all 6000+ users on one page, which leads to long delays. The default should be to show the first 25 users and there should be options to list 100, 250, or all users.
Purpose:
The reason behind adding this feature is also to make it the list of users easier to read, possibly reduce retrieval and loading time, and improve ease of navigation.

[[File:Img3.jpg|center|Proposal for division and navigation of pages]]

'''Proposal:'''
The yellow portion in the above screenshot is space we can use to add options to display 25, 100, 250, or all users at once, along with links to ‘previous’ and ‘next’ pages.

The following files will most likely be modified:
Models:
user.rb

Controllers:
users_controller.rb

Views:
users/list.html.erb
assignments/list_submissions.html.erb
grades/view.html.erb
review_mapping/response_report.html.haml
assessment360/all_students_all_reviews.html.erb

== Test Plan ==

Most of the testing for this project will be fairly simple.

All of the altered links will need to be tested to ensure they link to the correct pages. Tests that check if the username link correctly initiates impersonation of that user, and that clicking the full name links to the right user profile.

A test user needs to be created and the email link will be used to ensure emails are correctly sent.

For the second part of the project, tests need to be set up to check that the correct number of students are being displayed for each display option, and that the user can display subsequent pages of users.

File:Img3.JPG

2017-04-12T21:32:27Z

Fsmisarw:

File:Img2.JPG

2017-04-12T21:32:12Z

Fsmisarw:

File:Img1.JPG

2017-04-12T21:31:45Z

Fsmisarw:

CSC/ECE 517 Spring 2017/E1743

2017-04-12T21:31:15Z

Fsmisarw: Created page with "'''Problem:''' Expertiza has a feature that allows instructor i (or an admin) to impersonate a user whose account was created by i or recursively by a user that i created. Thi..."

'''Problem:'''

Expertiza has a feature that allows instructor i (or an admin) to impersonate a user whose account was created by i or recursively by a user that i created. This causes Expertiza to show what the impersonated user would see. It is good for tracking down bugs in what students see and also for accessing functionality that cannot be accessed from, or is too slow to access from, the instructor UI. Impersonating is currently performed by going to the pull-down menu at the top of the window and selecting Manage > Impersonate user. However, usually the instructor initiates impersonation after finding the student in some kind of list, like a list of users, or assignment participants, or as a member of a team signed up for a topic, etc. In this case, it is inconvenient to have to go to the pulldown menu and type in the user ID. It would be better if the instructor could just click on the ID in the list, and immediately have the impersonated user’s homepage show up.

Here’s what it currently looks like:

[[File:img1.jpg|center|Screenshot of the current Impersonate User page]]

'''Why''' we are working on the above stated problem:
The idea is to have more convenient options for instructors where a list of students is available, making it easier to both impersonate and view the details of any student with direct links.

[[File:img2.jpg|center|Proposal for Impersonate User links]]

'''Proposal:'''
Red: The student ID currently has a link that directs to the user profile page. We intend to change that to a link that would impersonate the user.
Blue: The user profile page link would be shifted to this column instead.
Green: A link on the email address which would invoke a mailto: HTML link.

The following screens do not currently show the user-ID, but we intend to modify them to do so.
View scores (User IDs could be shown below names in the Contributor column.)
View review report
Author feedback report (available from the pulldown menu on Review report).
Teammate review report ( “ “ “)

The '''second problem''' is that currently the default for Manage > Users is to list all 6000+ users on one page, which leads to long delays. The default should be to show the first 25 users and there should be options to list 100, 250, or all users.
Purpose:
The reason behind adding this feature is also to make it the list of users easier to read, possibly reduce retrieval and loading time, and improve ease of navigation.

[[File:img3.jpg|center|Proposal for division and navigation of pages]]

'''Proposal:'''
The yellow portion in the above screenshot is space we can use to add options to display 25, 100, 250, or all users at once, along with links to ‘previous’ and ‘next’ pages.

The following files will most likely be modified:
Models:
user.rb

Controllers:
users_controller.rb

Views:
users/list.html.erb
assignments/list_submissions.html.erb
grades/view.html.erb
review_mapping/response_report.html.haml
assessment360/all_students_all_reviews.html.erb

== Test Plan ==

Most of the testing for this project will be fairly simple.

All of the altered links will need to be tested to ensure they link to the correct pages. Tests that check if the username link correctly initiates impersonation of that user, and that clicking the full name links to the right user profile.

A test user needs to be created and the email link will be used to ensure emails are correctly sent.

For the second part of the project, tests need to be set up to check that the correct number of students are being displayed for each display option, and that the user can display subsequent pages of users.

CSC/ECE 517 Spring 2017/M1701

2017-04-01T02:15:11Z

Fsmisarw:

== Introduction ==

<big>'''Servo'''</big>

Servo<ref>https://en.wikipedia.org/wiki/Servo_(layout_engine)</ref> is a research project with the aim of creating a web browser layout engine written in Rust, being developed by Mozilla Research. The prototype of the system currently seeks to create a highly parallel environment in which many components are handled by fine-grained, isolated components. Servo provides a consistent API for hosting the engine within other software.Servo is still at an early stage of development. Servo can act as a standalone browser.

'''<big>Rust</big>'''

Rust<ref> https://en.wikipedia.org/wiki/Rust_(programming_language)</ref> is a general purpose, multi-paradigm, programming language sponsored, developed, and maintained by Mozilla Research for creating highly concurrent and highly safe systems. The development of Rust had an emphasis on control of memory layout, safety, and concurrency. It is very similar to C++ in terms of syntax but differs heavily in its semantics.

== Project Description ==

The repository www.github.com/servo/rust-har[http://www.github.com/servo/rust-har] is a library which implements HAR 1.2 spec in Rust. It was last changed two years ago and our task involved making it adhere to the syntax of the latest version of rust. The original code made use of some outdated code and syntax patterns. Our purpose was to make some key changes to those aspects of the code, that make it look better and such that it becomes more DRY.

The primary purpose of our contribution to the project was to add native support for the feature that enables the creation of HTTP archive files which can be analyzed by other tools. The addition of this feature to Servo allows more precise comparisons to be made with other browsers.
Our primary steps while working on the project involved<ref>https://github.com/servo/servo/wiki/HTTP-archive-support-project</ref>:

clone the rust-har repository and update the code to build with a modern version of Rust:
* remove/replace invalid integer suffixes
* replace box expressions with Box::new syntax
* replace use of serialize crate with serde_json
* add a new constructor for the Timing/CacheEntry/Cache/Content/Entry/Request/Response/Cookie/Header structures
* make the tests use the new constructor methods (cargo test)
* add TravisCI integration

== Design Pattern ==

No design pattern was needed/used in this project.

== Implementation ==

We have completed the above steps, and following are some of the snippets of code that were added or altered.
Here is the [https://github.com/servo/rust-har/pull/2 pull request] for this project.

Step 1: removing/replacing invalid integer suffixes
[[File:Screen1 1.png|center|removing/replacing invalid integer suffixes]]

Step 2: replacing box expressions with Box::new syntax

[[File:Screen1 2.png|center|replacing box expressions with Box::new syntax]]

Step 3: replacing use of serialize crate with serde_json

[[File:Screen1 3.png|center|replacing use of serialize crate with serde_json]]

Step 4: adding new constructors for the structures

[[File:Screen1 4.png|center|adding new constructors for the structures]]

Step 5: writing test cases to use the new constructors

[[File:Screen1 5.png|center|writing test cases to use the new constructors]]

== Testing ==

In terms of testing, we took care of the following:

1. We modified all test cases to implement "new constructor for structs"

2. Added a new test case 'test_page_timings_float' to verify that when a float value is passed for 'OptionalTiming'. We are asserting that deserializer returns an error.

3. When all syntax were modified to the latest version, only a few tests were failing due to camelCase issues. Those were fixed.

4. Earlier, we were asserting by comparing string. Now we see if two objects match.

== References ==

<references/>

CSC/ECE 517 Spring 2017/M1701

2017-04-01T00:23:25Z

Fsmisarw: /* Project Description */

CSC/ECE 517 Spring 2017/M1701

2017-03-23T18:48:04Z

Fsmisarw:

== Introduction ==

<big>'''Servo'''</big>

Servo<ref>https://en.wikipedia.org/wiki/Servo_(layout_engine)</ref> is a research project with the aim of creating a web browser layout engine written in Rust, being developed by Mozilla Research. The prototype of the system currently seeks to create a highly parallel environment in which many components are handled by fine-grained, isolated components. Servo provides a consistent API for hosting the engine within other software.Servo is still at an early stage of development. Servo can act as a standalone browser.

'''<big>Rust</big>'''

Rust<ref> https://en.wikipedia.org/wiki/Rust_(programming_language)</ref> is a general purpose, multi-paradigm, programming language sponsored, developed, and maintained by Mozilla Research for creating highly concurrent and highly safe systems. The development of Rust had an emphasis on control of memory layout, safety, and concurrency. It is very similar to C++ in terms of syntax but differs heavily in its semantics.

== Project Description ==

The repository www.github.com/servo/rust-har[http://www.github.com/servo/rust-har] is a library which implements HAR 1.2 spec in Rust. It was last changed two years ago and our task involved making it adhere to the syntax of the latest version of rust.

The primary purpose of our contribution to the project was to add native support for the feature that enables the creation of HTTP archive files which can be analyzed by other tools. The addition of this feature to Servo allows more precise comparisons to be made with other browsers.
Our primary steps while working on the project involved<ref>https://github.com/servo/servo/wiki/HTTP-archive-support-project</ref>:

clone the rust-har repository and update the code to build with a modern version of Rust:
* remove/replace invalid integer suffixes
* replace box expressions with Box::new syntax
* replace use of serialize crate with serde_json
* add a new constructor for the Timing/CacheEntry/Cache/Content/Entry/Request/Response/Cookie/Header structures
* make the tests use the new constructor methods (cargo test)
* add TravisCI integration

== Design Pattern ==

No design pattern was needed/used in this project.

== Implementation ==

We have completed the above steps, and following are some of the snippets of code that were added or altered.
Here is the [https://github.com/servo/rust-har/pull/2 pull request] for this project.

Step 1: removing/replacing invalid integer suffixes
[[File:Screen1 1.png|center|removing/replacing invalid integer suffixes]]

Step 2: replacing box expressions with Box::new syntax

[[File:Screen1 2.png|center|replacing box expressions with Box::new syntax]]

Step 3: replacing use of serialize crate with serde_json

[[File:Screen1 3.png|center|replacing use of serialize crate with serde_json]]

Step 4: adding new constructors for the structures

[[File:Screen1 4.png|center|adding new constructors for the structures]]

Step 5: writing test cases to use the new constructors

[[File:Screen1 5.png|center|writing test cases to use the new constructors]]

== References ==

<references/>

CSC/ECE 517 Spring 2017/M1701

2017-03-23T01:39:07Z

Fsmisarw:

== Introduction ==

<big>'''Servo'''</big>

Servo<ref>https://en.wikipedia.org/wiki/Servo_(layout_engine)</ref> is a research project with the aim of creating a web browser layout engine written in Rust, being developed by Mozilla Research. The prototype of the system currently seeks to create a highly parallel environment in which many components are handled by fine-grained, isolated components. Servo provides a consistent API for hosting the engine within other software.Servo is still at an early stage of development. Servo can act as a standalone browser.

'''<big>Rust</big>'''

Rust<ref> https://en.wikipedia.org/wiki/Rust_(programming_language)</ref> is a general purpose, multi-paradigm, programming language sponsored, developed, and maintained by Mozilla Research for creating highly concurrent and highly safe systems. The development of Rust had an emphasis on control of memory layout, safety, and concurrency. It is very similar to C++ in terms of syntax but differs heavily in its semantics.

== Project Description ==

The repository www.github.com/servo/rust-har[http://www.github.com/servo/rust-har] is a library which implements HAR 1.2 spec in Rust. It was last changed two years ago and our task involved making it adhere to the syntax of the latest version of rust.

The primary purpose of our contribution to the project was to add native support for the feature that enables the creation of HTTP archive files which can be analyzed by other tools. The addition of this feature to Servo allows more precise comparisons to be made with other browsers.
Our primary steps while working on the project involved<ref>https://github.com/servo/servo/wiki/HTTP-archive-support-project</ref>:

clone the rust-har repository and update the code to build with a modern version of Rust:
* remove/replace invalid integer suffixes
* replace box expressions with Box::new syntax
* replace use of serialize crate with serde_json
* add a new constructor for the Timing/CacheEntry/Cache/Content/Entry/Request/Response/Cookie/Header structures
* make the tests use the new constructor methods (cargo test)
* add TravisCI integration

== Design Pattern ==

No design pattern was needed/used in this project.

== Implementation ==

We have completed the above steps, and following are some of the snippets of code that were added or altered.

Step 1: removing/replacing invalid integer suffixes
[[File:Screen1 1.png|center|removing/replacing invalid integer suffixes]]

Step 2: replacing box expressions with Box::new syntax

[[File:Screen1 2.png|center|replacing box expressions with Box::new syntax]]

Step 3: replacing use of serialize crate with serde_json

[[File:Screen1 3.png|center|replacing use of serialize crate with serde_json]]

Step 4: adding new constructors for the structures

[[File:Screen1 4.png|center|adding new constructors for the structures]]

Step 5: writing test cases to use the new constructors

[[File:Screen1 5.png|center|writing test cases to use the new constructors]]

== References ==

<references/>

CSC/ECE 517 Spring 2017/M1701

2017-03-23T01:38:11Z

Fsmisarw: Created page with "== Introduction == <big>'''Servo'''</big> Servo<ref>https://en.wikipedia.org/wiki/Servo_(layout_engine)</ref> is a research project with the aim of creating a web browser layou..."

== Introduction ==

<big>'''Servo'''</big>

Servo<ref>https://en.wikipedia.org/wiki/Servo_(layout_engine)</ref> is a research project with the aim of creating a web browser layout engine written in Rust, being developed by Mozilla Research. The prototype of the system currently seeks to create a highly parallel environment in which many components are handled by fine-grained, isolated components. Servo provides a consistent API for hosting the engine within other software.Servo is still at an early stage of development. Servo can act as a standalone browser.

'''<big>Rust</big>'''

Rust<ref> https://en.wikipedia.org/wiki/Rust_(programming_language)</ref> is a general purpose, multi-paradigm, programming language sponsored, developed, and maintained by Mozilla Research for creating highly concurrent and highly safe systems. The development of Rust had an emphasis on control of memory layout, safety, and concurrency. It is very similar to C++ in terms of syntax but differs heavily in its semantics.

== Project Description ==

The repository www.github.com/servo/rust-har[http://www.github.com/servo/rust-har] is a library which implements HAR 1.2 spec in Rust. It was last changed two years ago and our task involved making it adhere to the syntax of the latest version of rust.

The primary purpose of our contribution to the project was to add native support for the feature that enables the creation of HTTP archive files which can be analyzed by other tools. The addition of this feature to Servo allows more precise comparisons to be made with other browsers.
Our primary steps while working on the project involved<ref>https://github.com/servo/servo/wiki/HTTP-archive-support-project</ref>:

clone the rust-har repository and update the code to build with a modern version of Rust:
* remove/replace invalid integer suffixes
* replace box expressions with Box::new syntax
* replace use of serialize crate with serde_json
* add a new constructor for the Timing/CacheEntry/Cache/Content/Entry/Request/Response/Cookie/Header structures
* make the tests use the new constructor methods (cargo test)
* add TravisCI integration

== Design Pattern ==

No design pattern was needed/used in this project.

== Implementation ==

We have completed the above steps, and following are some of the snippets of code that were added or altered.

Step 1: removing/replacing invalid integer suffixes
[[File:Screen1 1.png|center|removing/replacing invalid integer suffixes]]

Step 2: replacing box expressions with Box::new syntax

[[File:Screen1 2.png|center|replacing box expressions with Box::new syntax]]

Step 3: replacing use of serialize crate with serde_json

[[File:Screen1 3.png|center|replacing use of serialize crate with serde_json]]

Step 4: adding new constructors for the structures

[[File:Screen1 4.png|center|adding new constructors for the structures]]

Step 5: writing test cases to use the new constructors

[[File:Screen1 5.png|center|writing test cases to use the new constructors]]

== References ==

File:Screen1 5.png

2017-03-23T01:32:28Z

Fsmisarw: