User talk:Yjin6: Difference between revisions

From Expertiza_Wiki
Jump to navigation Jump to search
No edit summary
 
(4 intermediate revisions by 2 users not shown)
Line 3: Line 3:


== Problem Statement ==
== Problem Statement ==
E1624. Functional tests for suggested topic function
Contact: Zhewei Hu (zhu6@ncsu.edu)
What it does: Suggested topic functionality is designed for students to suggest topics they interested in. An assignment can be set up to allow students to suggest topics at the discretion of the instructor. Then, students can suggest topics, and add related descriptions. The proposer can state that (s)he wants to work on the suggested topic.  When the instructor approves a suggested topic, if the proposer wanted to work on it, it is assigned to the proposer. Otherwise, it is placed on the signup sheet for anyone to reserve. The purpose of suggested topic is to make the writing assignment more personalized.
What’s wrong with it:  Currently, there is no functional test for calibration function.
What needs to be done:
Understand the flow of the suggested topic function.
Do not use the development DB, otherwise your tests will not pass on TravisCI.
Create RSpec file in /spec/features/ folder.
Use fixtures to create the assignment record  and any other records such as participant records in test DB. 
Use Capybara to write functional tests for these three scenarios.
One team is on the waitlist. They sent a suggestion for new topic and they want to choose their suggested topic. After their suggested topic is approved, they should leave the waitlist and hold their suggested topic;
One team is holding a topic. They sent a suggestion for new topic and they want to choose their suggested topic. After their suggested topic is approved and they choose to switch to suggested topic, they will hold suggested topic and their old topic will be released. And if another team is in waitlist of that old topic, that team should hold the old topic now;
One team is holding a topic. They sent a suggestion for new topic and they do not want to work on their suggested topic. After their suggested topic is approved and they choose to public suggested topic, they will still hold their old topic. Their suggested topic will be added in sign-up sheet.
Create multiple tests to check valid and invalid cases.


===Files related===
===What it does===
Four models is related: criterion.rb, scale.rb, checkbox.rb, questionnaire_header.rb, upload_file.rb. There are 4 methods “edit”, “view_question_text”, “complete” and “view_completed_question” correspond to different views.  
Suggested topic functionality is designed for students to suggest topics they interested in. An assignment can be set up to allow students to suggest topics at the discretion of the instructor. Then, students can suggest topics, and add related descriptions. The proposer can state that (s)he wants to work on the suggested topic. When the instructor approves a suggested topic, if the proposer wanted to work on it, it is assigned to the proposer. Otherwise, it is placed on the signup sheet for anyone to reserve. The purpose of suggested topic is to make the writing assignment more personalized.
 
===What’s wrong with it===
*edit ~> when instructor add/edit new questions
Currently, there is no functional test for calibration function.
*view ~> when instructor view existed questions
===What needs to be done===
*complete ~> when students do peer reviews
*Understand the flow of the suggested topic function.
*view_completed_question ~> when student view existed peer reviews
*Do not use the development DB, otherwise your tests will not pass on TravisCI.
 
*Create RSpec file in /spec/features/ folder.
 
*Use fixtures to create the assignment record  and any other records such as participant records in test DB. 
 
*Use Capybara to write functional tests for these three scenarios.
===Expertiza question types inheritance hierarchy===
**One team is on the waitlist. They sent a suggestion for new topic and they want to choose their suggested topic. After their suggested topic is approved, they should leave the waitlist and hold their suggested topic;
**One team is holding a topic. They sent a suggestion for new topic and they want to choose their suggested topic. After their suggested topic is approved and they choose to switch to suggested topic, they will hold suggested topic and their old topic will be released. And if another team is in waitlist of that old topic, that team should hold the old topic now;
**One team is holding a topic. They sent a suggestion for new topic and they do not want to work on their suggested topic. After their suggested topic is approved and they choose to public suggested topic, they will still hold their old topic. Their suggested topic will be added in sign-up sheet.
*Create multiple tests to check valid and invalid cases.

Latest revision as of 19:42, 1 April 2016

This wiki page is for the description of changes made under E1624 OSS assignment for Spring 2016, CSC/ECE 517.


Problem Statement

What it does

Suggested topic functionality is designed for students to suggest topics they interested in. An assignment can be set up to allow students to suggest topics at the discretion of the instructor. Then, students can suggest topics, and add related descriptions. The proposer can state that (s)he wants to work on the suggested topic. When the instructor approves a suggested topic, if the proposer wanted to work on it, it is assigned to the proposer. Otherwise, it is placed on the signup sheet for anyone to reserve. The purpose of suggested topic is to make the writing assignment more personalized.

What’s wrong with it

Currently, there is no functional test for calibration function.

What needs to be done

  • Understand the flow of the suggested topic function.
  • Do not use the development DB, otherwise your tests will not pass on TravisCI.
  • Create RSpec file in /spec/features/ folder.
  • Use fixtures to create the assignment record and any other records such as participant records in test DB.
  • Use Capybara to write functional tests for these three scenarios.
    • One team is on the waitlist. They sent a suggestion for new topic and they want to choose their suggested topic. After their suggested topic is approved, they should leave the waitlist and hold their suggested topic;
    • One team is holding a topic. They sent a suggestion for new topic and they want to choose their suggested topic. After their suggested topic is approved and they choose to switch to suggested topic, they will hold suggested topic and their old topic will be released. And if another team is in waitlist of that old topic, that team should hold the old topic now;
    • One team is holding a topic. They sent a suggestion for new topic and they do not want to work on their suggested topic. After their suggested topic is approved and they choose to public suggested topic, they will still hold their old topic. Their suggested topic will be added in sign-up sheet.
  • Create multiple tests to check valid and invalid cases.
Retrieved from "https://wiki.expertiza.ncsu.edu/index.php?title=User_talk:Yjin6&oldid=101585"