Expertiza_Wiki - User contributions [en]

CSC/ECE 517 Spring 2023 - E2345. Reimplement QuestionnairesController and QuestionsController

2023-04-24T15:17:40Z

Asrivas7: /* Implementation */

==Introduction==
This page gives a description of the changes made for the ''questions_controller.rb, questionnaire_controller.rb, question.rb & questionnaire.rb'' of Expertiza based OSS project.

== Problem Statement ==
What is needed: This project builds on E2321, and the main goal is to get the endpoints of QuestionsController and QuestionnairesController running in reimplementation-backend repository. Detailed goals of the project are as follows:
#Improving the clarity and conciseness of code: The code should be written in a clean and concise manner. Methods with identical names that perform different functionalities should be renamed for clarity. Functions or functionality that are not clear should be commented on or removed. Any loops or methods that can be refactored for better performance should be addressed.
#Discarding unused functionality: Any unused functionality should be removed from the controllers. This will help to reduce complexity and make the code easier to maintain.
#Reimplement Question and Questionnaire models: Reimplement the two models to facilitate the endpoints of the respective controllers.
#Writing tests for the two models: Tests should be written for both the Questionnaires and the Questions models.
#Writing tests for the two controllers: Tests should be written for both the QuestionnairesController and the QuestionsController. The tests should written in the RSwag test format.

==General Design Goals==
* Ensure all prior/expected functionality is working correctly, and if not, make any repairs or changes necessary.
* Ensure that the each of the models and controllers have loose coupling and tight cohesion.
* DRY out prior implementation's controller and model methods which have functionality that already exists within the expertiza system.
* Ensure all present test cases still work properly after making the above changes and create additional test cases.

==Implementation==
The current implementation for the code can be found here [https://expertiza.csc.ncsu.edu/index.php?title=CSC/ECE_517_Spring_2023_-_E2321._Reimplement_QuestionnairesController_and_QuestionsController E2321]. 
To get the QuestionnairesController and QuestionsController endpoints running in the reimplementation-back-end repository, we need to reimplement the respective model files and add other dependent files. 

The following UML diagram shows the association between models we will be working on -

[[File:oodd_uml.png|border|800px|]]

Below is the implementation plan that we have followed for E2345:
<ol>
<li>
'''Implement basic version of ''question.rb'' and ''questionnaire.rb'' such that it facilitates the controllers' CRUD operations.''' 
:*Add required associations for ''user.rb, role.rb, question.rb, and questionnaire.rb'' only.
:*The below code snippets represent current implementation of ''question.rb'':
<pre>
class Question < ApplicationRecord
belongs_to :questionnaire # each question belongs to a specific questionnaire

validates :seq, presence: true, numericality: true # sequence must be numeric
validates :txt, length: { minimum: 0, allow_nil: false, message: "can't be nil" } # user must define text content for a question
validates :question_type, presence: true # user must define type for a question
validates :break_before, presence: true

def as_json(options = {})
super(options.merge({
only: %i[questionnaire_id txt weight seq question_type size alternatives break_before min_label max_label created_at updated_at],
include: {
questionnaire:
{ only: %i[name private min_question_score max_question_score instructor_id created_at updated_at questionnaire_type] }
}
})).tap do |hash|
hash['questionnaire'] ||= { id: nil, name: nil }
end
end

end
</pre>
In the above code, the as_json method is used to decorate the JSON object that is returned as a part of the response body from the controller endpoint. It is used to replace the questionnaire_id with the questionnaire details within the question object in JSON format.
:*The below code snippets represent current implementation of ''questionnaire.rb'':
<pre>
class Questionnaire < ApplicationRecord
has_many :questions, dependent: :restrict_with_error
belongs_to :instructor

before_destroy :check_for_question_associations

validate :validate_questionnaire
validates :name, presence: true
validates :max_question_score, :min_question_score, numericality: true

# clones the contents of a questionnaire, including the questions and associated advice
def self.copy_questionnaire_details(params)
orig_questionnaire = Questionnaire.find(params[:id])
questions = Question.where(questionnaire_id: params[:id])
questionnaire = orig_questionnaire.dup
questionnaire.name = 'Copy of ' + orig_questionnaire.name
questionnaire.created_at = Time.zone.now
questionnaire.updated_at = Time.zone.now
questionnaire.save!
questions.each do |question|
new_question = question.dup
new_question.questionnaire_id = questionnaire.id
new_question.save!
end
questionnaire
end

# validate the entries for this questionnaire
def validate_questionnaire
errors.add(:max_question_score, 'The maximum question score must be a positive integer.') if max_question_score < 1
errors.add(:min_question_score, 'The minimum question score must be a positive integer.') if min_question_score < 0
errors.add(:min_question_score, 'The minimum question score must be less than the maximum.') if min_question_score >= max_question_score
results = Questionnaire.where('id <> ? and name = ? and instructor_id = ?', id, name, instructor_id)
errors.add(:name, 'Questionnaire names must be unique.') if results.present?
end

# Check_for_question_associations checks if questionnaire has associated questions or not
def check_for_question_associations
if questions.any?
raise ActiveRecord::DeleteRestrictionError.new(:base, "Cannot delete record because dependent questions exist")
end
end

def as_json(options = {})
super(options.merge({
only: %i[id name private min_question_score max_question_score created_at updated_at questionnaire_type],
include: {
instructor: { only: %i[name email fullname password role] }
}
})).tap do |hash|
hash['instructor'] ||= { id: nil, name: nil }
end
end
end
</pre>
In the above code,
::*The as_json method is used to decorate the JSON object that is returned as a part of the response body from the controller endpoint. It is used to replace the instructor_id with the instructor details within the questionnaire object in JSON format.
::*The check_for_question_associations method is used to raise an Error if a Questionnaire that has associated questions is tried to be deleted.
::*The copy_questionnaire_details method is used to create a new object with the same attributes of the questionnaire and save it to the database. It is called when the copy endpoint is requested.
</li>
<li>
'''Reimplement ''questionnaires_controller.rb'' to incorporate the feedback received in E2321.''' 
:*index: This is a GET endpoint that responds with a list of all questionnaires with their attributes.
<pre>
def index
@questionnaires = Questionnaire.order(:id)
render json: @questionnaires, status: :ok and return
end
</pre>
:*show: This is a GET endpoint that accepts a questionnaire id and responds with the attributes of that questionnaire if it exists, otherwise provides with appropriate error.
<pre>
def show
begin
@questionnaire = Questionnaire.find(params[:id])
render json: @questionnaire, status: :ok and return
rescue ActiveRecord::RecordNotFound
render json: $ERROR_INFO.to_s, status: :not_found and return
end
end
</pre>
:*create: This is a POST endpoint that accepts the questionnaire parameters and creates a new questionnaire. Refactor the Create endpoint in ''questionnaires_controller.rb'' such that individual fields does not need to be set and validated. The below code represents the revised implementation of the method. A Questionnaire object is created using the new method instead of manual assignment of attributes.
<pre>
def create
begin
@questionnaire = Questionnaire.new(questionnaire_params)
@questionnaire.display_type = sanitize_display_type(@questionnaire.questionnaire_type)
@questionnaire.save!
render json: @questionnaire, status: :created and return
rescue ActiveRecord::RecordInvalid
render json: $ERROR_INFO.to_s, status: :unprocessable_entity
end
end
</pre>
:*destroy: This is a DELETE endpoint that accepts a questionnaire ID and deletes that questionnaire if it exists, otherwise provides with appropriate error. It should delete the questionnaire only if there are no questions associated to it.
<pre>
def destroy
begin
@questionnaire = Questionnaire.find(params[:id])
@questionnaire.delete
rescue ActiveRecord::RecordNotFound
render json: $ERROR_INFO.to_s, status: :not_found and return
rescue ActiveRecord::RecordInvalid
render json: $ERROR_INFO.to_s, status: :unprocessable_entity
end
end
</pre>
:*update: This is a PUT endpoint that accepts a questionnaire ID and parameters, and, updates that questionnaire with the given parameters if it exists, otherwise provides with appropriate error.
<pre>
def update
# Save questionnaire information
begin
@questionnaire = Questionnaire.find(params[:id])
@questionnaire.update(questionnaire_params)
@questionnaire.save!
render json: @questionnaire, status: :ok and return
rescue ActiveRecord::RecordNotFound
render json: $ERROR_INFO.to_s, status: :not_found and return
rescue ActiveRecord::RecordInvalid
render json: $ERROR_INFO.to_s, status: :unprocessable_entity
end
end
</pre>
:*copy: This is a POST endpoint that accepts a questionnaire ID and creates a new questionnaire (copy) with the same attributes of that questionnaire if it exists, otherwise provides with appropriate error.
<pre>
def copy
begin
@questionnaire = Questionnaire.copy_questionnaire_details(params)
render json: "Copy of the questionnaire has been created successfully.", status: :ok and return
rescue ActiveRecord::RecordNotFound
render json: $ERROR_INFO.to_s, status: :not_found and return
rescue ActiveRecord::RecordInvalid
render json: $ERROR_INFO.to_s, status: :unprocessable_entity
end
end
</pre>
:*toggle_access: This is a GET endpoint that changes the access from public to private and vice versa if it exists, otherwise provides with appropriate error.
<pre>
def toggle_access
begin
@questionnaire = Questionnaire.find(params[:id])
@questionnaire.private = !@questionnaire.private
@questionnaire.save!
@access = @questionnaire.private == true ? 'private' : 'public'
render json: "The questionnaire \"#{@questionnaire.name}\" has been successfully made #{@access}. ", status: :ok and return
rescue ActiveRecord::RecordNotFound
render json: $ERROR_INFO.to_s, status: :not_found and return
rescue ActiveRecord::RecordInvalid
render json: $ERROR_INFO.to_s, status: :unprocessable_entity
end
end
</pre>
</li>
<li>
'''Reimplement ''questions_controller.rb'' to incorporate the feedback received in E2321.''' 
:*index: This is a GET endpoint that responds with a list of all questions with their attributes.
<pre>
def index
@questions = Question.order(:id)
render json: @questions, status: :ok
end
</pre>
:*show: This is a GET endpoint that accepts a question id and responds with the attributes of that question if it exists, otherwise provides with appropriate error.
<pre>
def show
begin
@question = Question.find(params[:id])
render json: @question, status: :ok
rescue ActiveRecord::RecordNotFound
render json: $ERROR_INFO.to_s, status: :not_found
end
end
</pre>
:*create: This is a POST endpoint that accepts the question parameters and creates a new question. Refactor the Create endpoint in questions_controller.rb such that individual fields does not need to be set and validated. The below code represents the revised implementation of the method. A Question object is created using the new method instead of manual assignment of attributes.
<pre>
def create
begin
questionnaire_id = params[:questionnaire_id] unless params[:questionnaire_id].nil?
num_of_existed_questions = Questionnaire.find(questionnaire_id).questions.size
question = Question.create(
txt: params[:txt],
questionnaire_id: questionnaire_id,
seq: num_of_existed_questions + 1,
question_type: params[:question_type],
break_before: true)
case question.question_type
when 'Scale'
question.weight = params[:weight]
question.max_label = 'Strongly agree'
question.min_label = 'Strongly disagree'
when 'Cake', 'Criterion'
question.weight = params[:weight]
question.max_label = 'Strongly agree'
question.min_label = 'Strongly disagree'
question.size = '50, 3'
when 'Dropdown'
question.alternatives = '0|1|2|3|4|5'
question.size = nil
when 'TextArea'
question.size = '60, 5'
when 'TextField'
question.size = '30'
end

question.save!
render json: question, status: :created
rescue ActiveRecord::RecordNotFound
render json: $ERROR_INFO.to_s, status: :not_found and return
rescue ActiveRecord::RecordInvalid
render json: $ERROR_INFO.to_s, status: :unprocessable_entity
end
end
</pre>
:*destroy: This is a DELETE endpoint that accepts a question ID and deletes that question if it exists, otherwise provides with appropriate error.
<pre>
def destroy
begin
@question = Question.find(params[:id])
@question.destroy
rescue ActiveRecord::RecordNotFound
render json: $ERROR_INFO.to_s, status: :not_found and return
rescue ActiveRecord::RecordInvalid
render json: $ERROR_INFO.to_s, status: :unprocessable_entity
end
end
</pre>
:*delete_all: This is a DELETE endpoint that takes questionnaire_id as the path parameter and deletes all questions associated to that questionnaire. It returns status 404 if the questionnaire does not exist, status 422 if no questions are associated to that questionnaire and status 200 if all the questions are successfully deleted.
<pre>
def delete_all
begin
@questionnaire = Questionnaire.find(params[:id])
if @questionnaire.questions.size > 0
@questionnaire.questions.destroy_all
msg = "All questions for Questionnaire ID:" + params[:id].to_s + " has been successfully deleted!"
render json: msg, status: :ok
else
render json: "No questions associated to Questionnaire ID:" + params[:id].to_s, status: :unprocessable_entity and return
end
rescue ActiveRecord::RecordNotFound
render json: $ERROR_INFO.to_s, status: :not_found and return
rescue ActiveRecord::RecordInvalid
render json: $ERROR_INFO.to_s, status: :unprocessable_entity
end
end
</pre>
:*update: This is a PUT endpoint that accepts a question ID and parameters, and, updates that question with the given parameters if it exists, otherwise provides with appropriate error.
<pre>
def update
begin
@question = Question.find(params[:id])
@question.update(question_params)
@question.save!
render json: @question, status: :ok and return
rescue ActiveRecord::RecordNotFound
render json: $ERROR_INFO.to_s, status: :not_found and return
rescue ActiveRecord::RecordInvalid
render json: $ERROR_INFO.to_s, status: :unprocessable_entity
end
end
</pre>
:*types: This is a GET endpoint that responds with the list of question types.
<pre>
def types
types = Question.distinct.pluck(:question_type)
render json: types.to_a, status: :ok
end
</pre>
</li>
<li>
'''Write unit tests for Questions model and Questionnaires model using Rspec:''' Kindly refer to the Testing Methodology section for detailed description.
:*Unit tests for Question model: [https://github.com/Vineet2311/reimplementation-back-end/blob/main/spec/models/question_spec.rb question_spec.rb]
:*Unit tests for Questionnaire model: [https://github.com/Vineet2311/reimplementation-back-end/blob/main/spec/models/questionnaire_spec.rb questionnaire_spec.rb]
</li>
<li>
'''Write Rspec tests using Swagger API for each endpoint of QuestionsController and QuestionnairesController.''' Kindly refer to the Testing Methodology section for detailed description.
:*Swagger tests for QuestionsController: [https://github.com/Vineet2311/reimplementation-back-end/blob/main/spec/requests/api/v1/questions_spec.rb questions_spec.rb]
:*Swagger tests for QuestionnairesController: [https://github.com/Vineet2311/reimplementation-back-end/blob/main/spec/requests/api/v1/questionnaires_spec.rb questionnaires_spec.rb]
</li>
</ol>

==Testing Methodology==

Rspec test skeleton for QuestionnairesController and QuestionsController had been added in the previous project [https://expertiza.csc.ncsu.edu/index.php?title=CSC/ECE_517_Spring_2023_-_E2321._Reimplement_QuestionnairesController_and_QuestionsController E2321] but had not been executed due to missing dependencies. This project focuses on implementing them and getting automated test cases running as expected.
In our previous project we implemented the CRUD endpoints but since all the models were not present in reimplementation backend repository, we could only do manual testing of our controller endpoints using Postman. In this project, we focus to create the models required to implement CRUD operations in the reimplementation-back-end repository and test the endpoints using Swagger API.

====Controller Tests====

To run the controller tests:

#git clone
#cd reimplementation-back-end/
#bundle install
#rspec spec/requests/api/v1/questionnaires_controller_spec.rb
#rspec spec/requests/api/v1/questions_controller_spec.rb
#RAILS_ENV=test rails rswag

'''Tests for QuestionnairesController:''' [https://github.com/Vineet2311/reimplementation-back-end/blob/main/spec/requests/api/v1/questionnaires_spec.rb questionnaires_spec.rb]

{| class="wikitable" style="margin-left:30px"
|-
! Sr No !! Test Description
|-
| 1 || Test to create a new Questionnaire with valid parameters.
|-
| 2 || Test to create a new Questionnaire with invalid parameters.
|-
| 3 || Test to create a copy of Questionnaire with existing id in database.
|-
| 4 || Test to create a copy of Questionnaire with non-existing id in database.
|-
| 5 || Test to list the Questionnaires.
|-
| 6 || Test to update a Questionnaire with correct parameters.
|-
| 7 || Test to update a Questionnaire with incorrect parameters.
|-
| 8 || Test to update a Questionnaire with non-existing id in database.
|-
| 9 || Test to delete Questionnaire with existing id in database.
|-
| 10 || Test to delete Questionnaire with the non-existing id in database.
|-
| 11 || Test to show a Questionnaire with a existing id in database.
|-
| 12 || Test to show a Questionnaire with non-existing id in database.
|-
| 13 || Test to toggle private boolean flag of a Questionnaire with a existing id in database.
|-
| 14 || Test to toggle private boolean flag of a Questionnaire with non-existing id in database.
|}

[[File:Questionnaires_controller_test.jpeg|border|800px|]] 
[[File:Questionnaire_swagger.jpeg|border|800px|]]

'''Tests for QuestionsController:''' [https://github.com/Vineet2311/reimplementation-back-end/blob/main/spec/requests/api/v1/questions_spec.rb questions_spec.rb]

{| class="wikitable" style="margin-left:30px"
|-
! Sr No !! Test Description
|-
| 1 || Test to create a new Question with valid parameters.
|-
| 2 || Test to create a new Question with invalid parameters.
|-
| 3 || Test to create a new Question with non-existing Questionnaire id in the database
|-
| 4 || Test to list the Questions in the database.
|-
| 5 || Test to update the Question with correct parameters.
|-
| 6 || Test to update the Question with incorrect parameters.
|-
| 7 || Test to update the Question with non-existing id in the database.
|-
| 8 || Test to delete Question with existing id in the database.
|-
| 9 || Test to delete Question with the non-existing id in the database.
|-
| 10 || Test to show a Question with existing id in the database.
|-
| 11 || Test to show a Question with non-existing id in the database.
|-
| 12|| Test to get a types of Questions present in the database.
|-
| 13 || Test to delete all Questions of a Questionnaire with a valid Questionnaire id.
|-
| 14 || Test to delete all Questions of a Questionnaire with an invalid Questionnaire id.
|}

[[File:Questions_controller_test.jpeg|border|800px|]] 
[[File:Question_Swagger.jpeg|border|800px|]]

====Model Tests====

To run the model tests:

#git clone
#cd reimplementation-back-end/
#bundle install
#rspec spec/models/questionnaire_spec.rb
#rspec spec/models/question_spec.rb

'''Tests for Questionnaire model:''' [https://github.com/Vineet2311/reimplementation-back-end/blob/main/spec/models/questionnaire_spec.rb questionnaire_spec.rb]
{| class="wikitable" style="margin-left:30px"
|-
! Sr No !! Test Description
|-
| 1 || Test that Questionnaire requires a name.
|-
| 2 || Test validates the name of the questionnaire.
|-
| 3 || Test validates the instructor id in the questionnaire .
|-
| 4 || Test validates the maximum score in the questionnaire.
|-
| 5 || Test ensures maximum score of the questionnaire is an integer.
|-
| 6 || Test ensures maximum score is positive.
|-
| 7 || Test ensures maximum score is greater than the minimum score.
|-
| 8 || Test validates minimum score of a questionnaire.
|-
| 9 || Test ensures minimum score is smaller than maximum score.
|-
| 10 || Test ensures minimum score is an integer.
|-
| 11 || Test validates the association that a questionnaire comprises of several questions.
|-
| 12 || Test ensures that a questionnaire is not deleted when it has questions associated.
|-
| 13 || Test ensures calls from the method copy_questionnaire_details.
|-
| 14 || Test ensures creation of a copy of given questionnaire.
|-
| 15 || Test ensures creation of copy of all the present questionnaire in the database.
|}

[[File:Questionnaire_model_test.jpeg|border|800px|]]

'''Tests for Question model:''' [https://github.com/Vineet2311/reimplementation-back-end/blob/main/spec/models/question_spec.rb question_spec.rb]
{| class="wikitable" style="margin-left:30px"
|-
! Sr No !! Test Description
|-
| 1 || Test that Question has valid attributes defined.
|-
| 2 || Test ensures that a question is not valid without seq field.
|-
| 3 || Test that Question sequence number must be numerical.
|-
| 4 || Test ensures that a question is not valid without txt field.
|-
| 5 || Test ensures that a question is not valid without question_type field.
|-
|6|| Test ensures that a question is not valid without break_before field.
|-
|7|| Test ensures that a question does not exist without a questionnaire.
|-
|8|| Test ensures that a question object is deleted properly taking all its association into consideration.
|}

[[File:Question_model_test.jpeg|border|800px|]]

== Future Work ==
*The questions and questionnaires model in the reimplementation-back-end repo has been updated to have question_type and questionnaire_type attribute instead of type attribute. Ruby has implicit inheritance when the type attribute is used. However, our repo does not have the dependent models for each type of Question and Questionnaire. For future implementation, those model classes could be added and this attribute can be refactored in the model and controller files.
*Implement other associations (for example: assignments) within each models.

== Relevant Links ==
* '''Github Repository:''' https://github.com/Vineet2311/reimplementation-back-end
* '''Pull Request:''' https://github.com/expertiza/reimplementation-back-end/pull/20
* '''VCL Server:''' http://152.7.178.189:8080
* '''Test Video Link:'''

==Contributors==
This feature was created as part of Dr. Edward Gehringer's "CSC/ECE 517: Object-Oriented Design and Development" class, Spring 2023. The contributors were: Vineet Vimal Chheda, Rohan Jigarbhai Shah, and Aditya Srivastava. Our project mentor was Ankur Mundra (amundra@ncsu.edu)

File:Oodd uml.png

2023-04-24T15:16:12Z

Asrivas7:

CSC/ECE 517 Spring 2023 - E2345. Reimplement QuestionnairesController and QuestionsController

2023-04-13T00:09:22Z

Asrivas7: /* Current Implementation */

CSC/ECE 517 Spring 2023 - E2345. Reimplement QuestionnairesController and QuestionsController

2023-04-13T00:05:10Z

Asrivas7: /* Current Implementation */

CSC/ECE 517 Spring 2023 - E2345. Reimplement QuestionnairesController and QuestionsController

2023-04-13T00:00:08Z

Asrivas7: /* Model Tests */

CSC/ECE 517 Spring 2023 - E2345. Reimplement QuestionnairesController and QuestionsController

2023-04-12T23:56:19Z

Asrivas7: /* Testing Methodology */

CSC/ECE 517 Spring 2023 - E2345. Reimplement QuestionnairesController and QuestionsController

2023-04-12T23:32:18Z

Asrivas7: /* Testing Methodology */

CSC/ECE 517 Spring 2023 - E2345. Reimplement QuestionnairesController and QuestionsController

2023-04-12T23:26:05Z

Asrivas7: /* Testing Methodology */

CSC/ECE 517 Spring 2023 - E2345. Reimplement QuestionnairesController and QuestionsController

2023-04-12T23:15:17Z

Asrivas7: /* Implementation Plan */

CSC/ECE 517 Spring 2023 - E2345. Reimplement QuestionnairesController and QuestionsController

2023-04-12T23:14:12Z

Asrivas7: /* Implementation Plan */

CSC/ECE 517 Spring 2023 - E2345. Reimplement QuestionnairesController and QuestionsController

2023-04-12T23:13:14Z

Asrivas7: /* Implementation Plan */

CSC/ECE 517 Spring 2023 - E2345. Reimplement QuestionnairesController and QuestionsController

2023-04-12T23:08:20Z

Asrivas7: /* Implementation Plan */

File:UML diagram 2345.png

2023-04-12T23:06:02Z

Asrivas7:

CSC/ECE 517 Spring 2023 - E2321. Reimplement QuestionnairesController and QuestionsController

2023-03-23T03:13:27Z

Asrivas7:

'''E2321. Reimplement QuestionnairesController and QuestionsController'''

==Problem Statement==
The questionnaire is the superclass for all kinds of questionnaires and rubrics. Rubrics are used for evaluating submissions and teammate contributions, as well as taking quizzes and surveys, and all of these are subclasses of the Questionnaire class. In Expertiza, various types of questionnaires can be created, such as the Survey Questionnaire, Author Feedback Questionnaire, Bookmark Rating Questionnaire, Metareview Questionnaire, Quiz Questionnaire, Review Questionnaire, and Teammate Review Questionnaire. Each of these questionnaires can have zero or more questions, which are represented by the Question class. Typically, a questionnaire is associated with an assignment using the Assignment class.

The Questionnaire Controller is responsible for performing CRUD (Create, Read, Update, Delete) operations, such as copying and viewing questionnaires. On the other hand, the Questions Controller is responsible for creating, modifying, and deleting individual questions within a questionnaire. Questions can come in various types, such as checkboxes, multiple choice, text boxes, and more. However, each question object will always belong to a particular questionnaire. However, the current implementation suffers from several issues, such as mixing the responsibilities of the two controllers, using methods with identical names for different functionalities, and unclear or unused functionalities. Therefore, to improve the code quality and functionality, the two controllers should be implemented separately and adhere to the CRUD operations as much as possible. Additionally, the code needs to be refactored and optimized for better performance, and unused or unclear methods should be discarded. Finally, comprehensive tests should be written to ensure that the code is functioning correctly and free of code smells.

==Goals of this Project==
The goals of this Project are:

#Separating the responsibilities of the QuestionnairesController and QuestionsController
#Fix bugs in the existing functionality
#Implementing CRUD operations for each controller
#Discarding unused or unclear functionality
#Writing tests for the two controllers

By achieving these goals, both the controllers can have their basic CRUD functionalities as well as it will also ensure that the code readability and functionality of the code for the two controllers is increased. It will also help in resolving the existing bugs which will increase correctness of the code.

==Implementation==

A considerable amount of time and effort was necessary to review, understand, and re-implement the previous implementation of QuestionsController and QuestionnairesController. The team started with understanding how the Questionnaires and Questions module work by playing around with the Expertiza website. Once we had understanding of the flow, we started understanding the existing code written in the controllers. At first glance, it was visible that the QuestionnairesController was handling all the CRUD operations of Questions as well. We identified what functionalities did not belong in the QuestionnairesController and which redundant code had to be removed. The issues that we have addressed in our reimplementation project are listed as follows.

#'''Separating the responsibilities of the QuestionnairesController and QuestionsController:''' Initially the add_new_questions method present in questionnaire controller was responsible for adding a new question for the given questionnaire. As questions controller is responsible for creating a question, we defined a create method in questions controller which is responsible for the adding a new question for a given questionnaire. Since, to link a question to a questionnaire, we passed questionnaire_id using params and linked a new question created with the help of create method in questions controller to the required questionnaire and thus separated their responsibilities.
#'''Discard unused functionality and redundant code:'''
#'''Minor Bug fixes in the existing code:''' The following bugs in the existing code needed to be fixed.
##User was not able to delete Questionnaire: After careful debugging, we found that a path for delete questionnaire was not defined in the routes.rb file.
##Nil Class Error while saving empty questionnaire: We kept a check in the save_all_questions method to handle the error and allow the questionnaire to be saved empty.
#'''Fix the update method in QuestionnairesController:''' The original implementation of the method could not update the attributes of the questionnaire and it was used only to update the questions of that questionnaire. We reimplemented the method to update both the questionnaire attributes and each question if a change was made to them.
#'''Reimplement CRUD functionality and create JSON endpoints in QuestionsController:''' We reimplemented the following methods to create the required endpoints in [https://github.com/expertiza/reimplementation-back-end/blob/0b09c15466e5d9865663ed2253d9f37a2e1ca1d9/app/controllers/api/v1/questions_controller.rb questions_controller.rb].
##index: This is a GET endpoint that responds with a list of all questions with their attributes.
##show: This is a GET endpoint that accepts a question id and responds with the attributes of that question if it exists.
##create: This is a POST endpoint that accepts the question parameters and creates a new question.
##destroy: This is a DELETE endpoint that accepts a question ID and deletes that question.
##update: This is a PUT endpoint that accepts a question ID and parameters, and, updates that question with the given parameters.
##types: This is a GET endpoint that responds with the list of question types.
#'''Reimplement CRUD functionality and create JSON endpoints in QuestionnairesController:''' We reimplemented the following methods to create the required endpoints in [https://github.com/expertiza/reimplementation-back-end/blob/0b09c15466e5d9865663ed2253d9f37a2e1ca1d9/app/controllers/api/v1/questionnaires_controller.rb questionnaires_controller.rb].
##index: This is a GET endpoint that responds with a list of all questionnaires with their attributes.
##show: This is a GET endpoint that accepts a questionnaire id and responds with the attributes of that questionnaire if it exists.
##create: This is a POST endpoint that accepts the questionnaire parameters and creates a new questionnaire.
##destroy: This is a DELETE endpoint that accepts a questionnaire ID and deletes that questionnaire.
##update: This is a PUT endpoint that accepts a questionnaire ID and parameters, and, updates that questionnaire with the given parameters.
##copy: This is a POST endpoint that accepts a questionnaire ID and creates a new questionnaire (copy) with the same attributes of that questionnaire.
##toggle_access: This is a GET endpoint that changes the access from public to private and vice versa.

==Testing Methodology==
Our work was to reimplement the QuestionsController.rb and QuestionnairesController.rb and create JSON endpoints for each CRUD operation. Since all the operations had dependencies on other Models and Helper functions which are not included in the reimplementation-back-end, it is not possible for us to use RSpec as the testing tool. To test each endpoint, we have used Postman to send a request to each endpoint. The video with the testing is available at https://bit.ly/E2321

== Relevant Links ==
* '''Github Repository:''' https://github.com/Vineet2311/reimplementation-back-end
* '''Pull Request:''' https://github.com/expertiza/reimplementation-back-end/pull/20
* '''VCL Server:''' http://152.7.177.38:8080
* '''Test Link:''' https://bit.ly/E2321

==Contributors==
This feature was created as part of Dr. Edward Gehringer's "CSC/ECE 517: Object-Oriented Design and Development" class, Spring 2023. The contributors were: Vineet Vimal Chheda, Rohan Jigarbhai Shah, and Aditya Srivastava. Our project mentor was Ankur Mundra (amundra@ncsu.edu)

CSC/ECE 517 Spring 2023 - E2321. Reimplement QuestionnairesController and QuestionsController

2023-03-23T02:38:44Z

Asrivas7:

'''E2321. Reimplement QuestionnairesController and QuestionsController'''

==Problem Statement==
The questionnaire is the superclass for all kinds of questionnaires and rubrics. Rubrics are used for evaluating submissions and teammate contributions, as well as taking quizzes and surveys, and all of these are subclasses of the Questionnaire class. In Expertiza, various types of questionnaires can be created, such as the Survey Questionnaire, Author Feedback Questionnaire, Bookmark Rating Questionnaire, Metareview Questionnaire, Quiz Questionnaire, Review Questionnaire, and Teammate Review Questionnaire. Each of these questionnaires can have zero or more questions, which are represented by the Question class. Typically, a questionnaire is associated with an assignment using the Assignment class.

The Questionnaire Controller is responsible for performing CRUD (Create, Read, Update, Delete) operations, such as copying and viewing questionnaires. On the other hand, the Questions Controller is responsible for creating, modifying, and deleting individual questions within a questionnaire. Questions can come in various types, such as checkboxes, multiple choice, text boxes, and more. However, each question object will always belong to a particular questionnaire. However, the current implementation suffers from several issues, such as mixing the responsibilities of the two controllers, using methods with identical names for different functionalities, and unclear or unused functionalities. Therefore, to improve the code quality and functionality, the two controllers should be implemented separately and adhere to the CRUD operations as much as possible. Additionally, the code needs to be refactored and optimized for better performance, and unused or unclear methods should be discarded. Finally, comprehensive tests should be written to ensure that the code is functioning correctly and free of code smells.

==Goals of this Project==
The goals of this Project are:

#Separating the responsibilities of the QuestionnairesController and QuestionsController
#Fix bugs in the existing functionality
#Implementing CRUD operations for each controller
#Discarding unused or unclear functionality
#Writing tests for the two controllers

By achieving these goals, both the controllers can have their basic CRUD functionalities as well as it will also ensure that the code readability and functionality of the code for the two controllers is increased. It will also help in resolving the existing bugs which will increase correctness of the code.

==Implementation==

A considerable amount of time and effort was necessary to review, understand, and re-implement the previous implementation of QuestionsController and QuestionnairesController. The team started with understanding how the Questionnaires and Questions module work by playing around with the Expertiza website. Once we had understanding of the flow, we started understanding the existing code written in the controllers. At first glance, it was visible that the QuestionnairesController was handling all the CRUD operations of Questions as well. We identified what functionalities did not belong in the QuestionnairesController and which redundant code had to be removed. The issues that we have addressed in our reimplementation project are listed as follows.

#Separating the responsibilities of the QuestionnairesController and QuestionsController: Initially the add_new_questions method present in questionnaire controller was responsible for adding a new question for the given questionnaire. As questions controller is responsible for creating a question, we defined a create method in questions controller which is responsible for the adding a new question for a given questionnaire. Since, to link a question to a questionnaire, we passed questionnaire_id using params and linked a new question created with the help of create method in questions controller to the required questionnaire and thus separated their responsibilities.
#Minor Bug fixes in the existing code: The following bugs in the existing code needed to be fixed.
##User was not able to delete Questionnaire: After careful debugging, we found that a path for delete questionnaire was not defined in the routes.rb file.
##Nil Class Error while saving empty questionnaire: We kept a check in the save_all_questions method to handle the error and allow the questionnaire to be saved empty.
#Fix the update method in QuestionnairesController: The original implementation of the method could not update the attributes of the questionnaire and it was used only to update the questions of that questionnaire. We reimplemented the method to update both the questionnaire attributes and each question if a change was made to them.
#Reimplement CRUD functionality and create JSON endpoints in QuestionsController: We reimplemented the following methods to create the required endpoints.
##index: This is a GET endpoint that responds with a list of all questions with their attributes.
##show: This is a GET endpoint that accepts a question id and responds with the attributes of that question if it exists.
##create: This is a POST endpoint that accepts the question parameters and creates a new question.
##destroy: This is a DELETE endpoint that accepts a question ID and deletes that question.
##update: This is a PUT endpoint that accepts a question ID and parameters, and, updates that question with the given parameters.
#Reimplement CRUD functionality and create JSON endpoints in QuestionnairesController: We reimplemented the following methods to create the required endpoints.
##index: This is a GET endpoint that responds with a list of all questionnaires with their attributes.
##show: This is a GET endpoint that accepts a questionnaire id and responds with the attributes of that questionnaire if it exists.
##create: This is a POST endpoint that accepts the questionnaire parameters and creates a new questionnaire.
##destroy: This is a DELETE endpoint that accepts a questionnaire ID and deletes that questionnaire.
##update: This is a PUT endpoint that accepts a questionnaire ID and parameters, and, updates that questionnaire with the given parameters.
##copy: This is a POST endpoint that accepts a questionnaire ID and creates a new questionnaire (copy) with the same attributes of that questionnaire.

==Testing Methodology==
Our work was to reimplement the QuestionsController.rb and QuestionnairesController.rb and create JSON endpoints for each CRUD operation. Since all the operations had dependencies on other Models and Helper functions which are not included in the reimplementation-back-end, it is not possible for us to use RSpec as the testing tool. To test each endpoint, we have used Postman to send a request to each endpoint. The video with the testing is available at https://bit.ly/E2321

== Relevant Links ==
* '''Github Repository:''' https://github.com/Vineet2311/reimplementation-back-end
* '''Pull Request:''' https://github.com/expertiza/reimplementation-back-end/pull/20
* '''VCL Server:''' http://152.7.177.38:8080
* '''Test Link:''' https://bit.ly/E2321

==Contributors==
This feature was created as part of Dr. Edward Gehringer's "CSC/ECE 517: Object-Oriented Design and Development" class, Spring 2023. The contributors were: Vineet Vimal Chheda, Rohan Jigarbhai Shah, and Aditya Srivastava. Our project mentor was Ankur Mundra (amundra@ncsu.edu)

CSC/ECE 517 Spring 2023 - E2321. Reimplement QuestionnairesController and QuestionsController

2023-03-23T02:31:41Z

Asrivas7: Update Implementation

'''E2321. Reimplement QuestionnairesController and QuestionsController'''

==Problem Statement==
The questionnaire is the superclass for all kinds of questionnaires and rubrics. Rubrics are used for evaluating submissions and teammate contributions, as well as taking quizzes and surveys, and all of these are subclasses of the Questionnaire class. In Expertiza, various types of questionnaires can be created, such as the Survey Questionnaire, Author Feedback Questionnaire, Bookmark Rating Questionnaire, Metareview Questionnaire, Quiz Questionnaire, Review Questionnaire, and Teammate Review Questionnaire. Each of these questionnaires can have zero or more questions, which are represented by the Question class. Typically, a questionnaire is associated with an assignment using the Assignment class.

The Questionnaire Controller is responsible for performing CRUD (Create, Read, Update, Delete) operations, such as copying and viewing questionnaires. On the other hand, the Questions Controller is responsible for creating, modifying, and deleting individual questions within a questionnaire. Questions can come in various types, such as checkboxes, multiple choice, text boxes, and more. However, each question object will always belong to a particular questionnaire. However, the current implementation suffers from several issues, such as mixing the responsibilities of the two controllers, using methods with identical names for different functionalities, and unclear or unused functionalities. Therefore, to improve the code quality and functionality, the two controllers should be implemented separately and adhere to the CRUD operations as much as possible. Additionally, the code needs to be refactored and optimized for better performance, and unused or unclear methods should be discarded. Finally, comprehensive tests should be written to ensure that the code is functioning correctly and free of code smells.

==Goals of this Project==
The goals of this Project are:

#Separating the responsibilities of the QuestionnairesController and QuestionsController
#Fix bugs in the existing functionality
#Implementing CRUD operations for each controller
#Discarding unused or unclear functionality
#Writing tests for the two controllers

By achieving these goals, both the controllers can have their basic CRUD functionalities as well as it will also ensure that the code readability and functionality of the code for the two controllers is increased. It will also help in resolving the existing bugs which will increase correctness of the code.

==Implementation==

A considerable amount of time and effort was necessary to review, understand, and re-implement the previous implementation of QuestionsController and QuestionnairesController. The team started with understanding how the Questionnaires and Questions module work by playing around with the Expertiza website. Once we had understanding of the flow, we started understanding the existing code written in the controllers. At first glance, it was visible that the QuestionnairesController was handling all the CRUD operations of Questions as well. We identified what functionalities did not belong in the QuestionnairesController and which redundant code had to be removed. The issues that we have addressed in our reimplementation project are listed as follows.

#Separating the responsibilities of the QuestionnairesController and QuestionsController: Initially the add_new_questions method present in questionnaire controller was responsible for adding a new question for the given questionnaire. As questions controller is responsible for creating a question, we defined a create method in questions controller which is responsible for the adding a new question for a given questionnaire. Since, to link a question to a questionnaire, we passed questionnaire_id using params and linked a new question created with the help of create method in questions controller to the required questionnaire and thus separated their responsibilities.
#Minor Bug fixes in the existing code: The following bugs in the existing code needed to be fixed.
##User was not able to delete Questionnaire: After careful debugging, we found that a path for delete questionnaire was not defined in the routes.rb file.
##Nil Class Error while saving empty questionnaire: We kept a check in the save_all_questions method to handle the error and allow the questionnaire to be saved empty.
#Fix the update method in QuestionnairesController: The original implementation of the method could not update the attributes of the questionnaire and it was used only to update the questions of that questionnaire. We reimplemented the method to update both the questionnaire attributes and each question if a change was made to them.
#Reimplement CRUD functionality and create JSON endpoints in QuestionsController: We reimplemented the following methods to create the required endpoints.
##index: This is a GET endpoint that responds with a list of all questions with their attributes.
##show: This is a GET endpoint that accepts a question id and responds with the attributes of that question if it exists.
##create: This is a POST endpoint that accepts the question parameters and creates a new question.
##destroy: This is a DELETE endpoint that accepts a question ID and deletes that question.
##update: This is a PUT endpoint that accepts a question ID and parameters, and, updates that question with the given parameters.
#Reimplement CRUD functionality and create JSON endpoints in QuestionnairesController: We reimplemented the following methods to create the required endpoints.
##index: This is a GET endpoint that responds with a list of all questionnaires with their attributes.
##show: This is a GET endpoint that accepts a questionnaire id and responds with the attributes of that questionnaire if it exists.
##create: This is a POST endpoint that accepts the questionnaire parameters and creates a new questionnaire.
##destroy: This is a DELETE endpoint that accepts a questionnaire ID and deletes that questionnaire.
##update: This is a PUT endpoint that accepts a questionnaire ID and parameters, and, updates that questionnaire with the given parameters.

==Testing Methodology==
Our work was to reimplement the QuestionsController.rb and QuestionnairesController.rb and create JSON endpoints for each CRUD operation. Since all the operations had dependencies on other Models and Helper functions which are not included in the reimplementation-back-end, it is not possible for us to use RSpec as the testing tool. To test each endpoint, we have used Postman to send a request to each endpoint. The video with the testing is available at https://bit.ly/E2321

== Relevant Links ==
* '''Github Repository:''' https://github.com/Vineet2311/reimplementation-back-end
* '''Pull Request:''' https://github.com/expertiza/reimplementation-back-end/pull/20
* '''VCL Server:''' http://152.7.177.38:8080
* '''Test Link:''' https://bit.ly/E2321

==Contributors==
This feature was created as part of Dr. Edward Gehringer's "CSC/ECE 517: Object-Oriented Design and Development" class, Spring 2023. The contributors were: Vineet Vimal Chheda, Rohan Jigarbhai Shah, and Aditya Srivastava. Our project mentor was Ankur Mundra (amundra@ncsu.edu)