E1726 - Remove Cache Field in Roles Table

Introduction

Background

Expertiza is an open source web-based peer review system developed using Ruby on Rails. It is a dashboard containing all assignments for a particular course which is managed by the Professors and Teaching Assistants.

It eases the process of selecting assignment topics and choosing team-mates for the projects and greatly reduces the burden on the Professors and Teaching Assistants of assigning and managing teams for each assignment.

The main motive of this project is to make learning more effective through peer review. It allows students to review each other’s work and improve their work upon this feedback. It not only helps one improve their work but also provides a new way to learn.

Students upload or provide URLs of their work on expertiza which would be reviewed by the instructors and peers. Students later get to improve their work based on the reviews provided their peers.

Problem statement : Remove cache field in roles table

The project requires us to remove the cache column from the roles table in database. Expertiza's 'roles' table has a 'cache' column, used by the superfish-rails gem to display different menus for different roles(super-administrator, administrator, instructor, teaching assistant, student, and unregistered user).

There is a Role model which makes use of the long text string data stored in the roles table under the cache column to load the menus (e.g., Users \n Questionnaires \n Courses …) for a particular role at the top of the page after login. Storing such long strings in databases is a bad idea because if we want to change that large text we are required to write a migration file which would be inconvenient and also there is a restriction on the number of characters allowed for long string datatype in MySQL.

We can resolve it by modifying the lines during cache attribute value assignment in the model. But the problem is that it will make the data used by different users inconsistent. We can work around this modification in an easy fashion, if we could store the large strings in the YAML files (one file for each role in the database)

Tasks Identified

1. Create YAML files containing the cache column data for each role from roles table in database.
   1. Create YAML files under 'config' folder named 'role_admin.yml' and put the 'cache' column value in it split across rails environment
   2. Create ruby script under 'config/initializers' folder named 'load_roles.rb' - to load the corresponding YAML values once the environment is set up
2. Change the role.rb model to facilitate the use of above defined YAML files
3. Remove the cache column from the roles table by migration
4. Write rspec unit test for 'role.rb'

Implementation

Created YAML files containing the cache column data for each role from roles table in database

Created YAML files under 'config' folder named 'role_admin.yml' and put the 'cache' column value in it split across rails environment

• 6 new files (role_admin.yml, role_instructor.yml, role_student.yml, role_super_admin.yml, role_ta.yml, role_unreg_user.yml)  each corresponding to specific role are created
• Content of cache column from roles table are added for development, production and test environments

Created ruby script under 'config/initializers' folder named 'load_roles.rb' - to load the corresponding YAML values once the environment is set up

This code loads content of "/config/role_admin.yml" file and assigns to CACHED_ADMIN_MENU. Similarly, fields corresponding to different roles are populated from corresponding "/config/role_[ROLE]_.yml" file

Changed the role.rb model to facilitate the use of above defined YAML files

Rebuid_credentials and rebuild_menu method are modified to load content from yml file. Here ApplicationHelper exposes get_cache_roles method to retrieve cache content corresponding to role id.

In rebuild_cache method, role.save line is removed as cache field is not saved in database now. Since cache field is removed from roles table, this field is added to role model  using attr_accessible. It’s getter and setter are also created

Removed the cache column from the roles table by migration

Before removing cache column in roles table

Roles table after removing cache column

Migration file to drop cache column

Test Plan

The test plan followed here is done across 3 roles namely, student, administrator and instructor. The scenarios covered here are as follows: Scenario 1: Check for the cache field and see if we get the same expected value. Scenario 2: Check if the role is valid role. Scenario 3: Check for the cache field mismatch, that is, invalid cache field match. The sections below points out the steps taken to cover the test plan described above.

UI Testing

1. Login into Expertiza as one of the roles - super-admin or admin or student or instructor
2. Check the menu tabs on the top and you can find the respective drop-downs according to the role logged in
3. On clicking the option from the drop down you will be able to navigate to the respective pages
4. This ensures that the code change done by us didn't break the code and it delivered it's expected functionality

Unit Testing

Unit tests have been written to check whether the modules work as it did earlier before. We have written rspec unit test for ‘role.rb’ which can be found here: ‘spec/models/role_spec.rb’ which tests 10 cases

1. Evaluate the cache value with YAML values for student
2. Evaluate the cache value with YAML values for instructor
3. Evaluate the cache value with YAML values for admin
4. Validation of name for student
5. Validation of name for instructor
6. Validation of name for admin
7. Check the mismatch for cache values for the student in factories.rb
8. Check the mismatch for cache values for the instructor in factories.rb
9. Check the mismatch for cache values for the admin in factories.rb
10. An invalid check for role object

Manual Testing

Steps:

1) cd into the expertiza directory

2) Run the command: rspec spec/models/role_spec.rb

Scope for future improvement

There is a lot of scope for improvement for the current code. For instance, in the present situation, the YAML files have the database data corresponding to menu_items hard coded. We could define YAML file for menu_items table and load the menu_item YAML into the corresponding role YAML during environment setup. This would eradicate the use of menu_item table from the database.