E1936 Specialized Rubrics: Difference between revisions
Jump to navigation
Jump to search
Line 7: | Line 7: | ||
===Problem Statement=== | ===Problem Statement=== | ||
In CSC/ECE 517, there are several types of topics that could be covered in a single class assignment. | |||
* Code base | |||
* | ** Expertiza | ||
** Mozilla | |||
** etc. | |||
* Goal | |||
** Refactoring | |||
** Testing | |||
** etc. | |||
However, currently we can only specify one kind of rubric for an assignment. This means that teams working on different topics will be evaluated using the same rubric. | |||
===Current Implementation=== | ===Current Implementation=== |
Revision as of 16:04, 2 April 2019
E1936. Specialized Rubrics for Different Topic Types
This page provides a description of an Expertiza OSS project.
Problem Statement
In CSC/ECE 517, there are several types of topics that could be covered in a single class assignment.
- Code base
- Expertiza
- Mozilla
- etc.
- Goal
- Refactoring
- Testing
- etc.
However, currently we can only specify one kind of rubric for an assignment. This means that teams working on different topics will be evaluated using the same rubric.
Current Implementation
Functionality
- (TODO)
Problems and Solutions
The problems listed below are examples of the four main classes of problems we encountered with Expertiza authorization. This is not an exhaustive list of problems, but is a good representation of the classes of problems addressed.
- Problem 1: (TODO)
(TODO)
- Solution 1: (TODO)
(TODO)
New Implementation
- (TODO)
(TODO)
How to Add a New Rubric
- (TODO)
How to Select a Rubric for a Topic
- (TODO)
Automated Testing with RSPEC
Our strategy for gaining confidence that our code changes did not break anything was as follows:
- Run all existing RSpec tests on any changed files, after our changes, to ensure that we have not introduced any failures.
- The commands and results are shown below.
(TODO)
- Write new comprehensive RSpec tests, for all new methods.
- Run these tests, to ensure that the new code works as intended.
- The commands and results are shown below.
(TODO)
- The test suite for a single new method is below.
- There are many such suites in (TODO add filename(s)).
- This example illustrates our general strategy:
- test missing input
- test bad input
- test various acceptable forms of input
- test scenarios that lead to "true" and to "false" return values
(TODO)
Team Members
- Aurora Tiffany-Davis
- Ginger Balmat
- Joe Hutchinson
- Nikolay Titov
Links (Our Work)
- [(add link here) Project Repository Fork]
- [(add link here) Pull Request]
- [(add link here) Video Demonstration of Specialized Rubrics]