Skip to content

assessment updates part 1#428

Merged
LolaValente merged 3 commits intomasterfrom
AssessmentsUpdate
Oct 30, 2025
Merged

assessment updates part 1#428
LolaValente merged 3 commits intomasterfrom
AssessmentsUpdate

Conversation

@LolaValente
Copy link
Collaborator

@LolaValente LolaValente commented Oct 30, 2025

Summary by CodeRabbit

  • Documentation
    • Reorganized and clarified assessment authoring with a new common-configuration section and step-by-step "How to Add a New Assessment."
    • Added AI-generated assessment guidance, example prompts, and a "How to Generate Assessment with AI" workflow (with note that layout must be set manually).
    • Introduced "Auto-Graded Assessment Types" and standardized "Test Types" guidance.
    • Expanded secure-folder/file-organization, student workspace limits, and updated examples/visuals for consistency.

@LolaValente LolaValente requested a review from shajason October 30, 2025 19:40
@coderabbitai
Copy link

coderabbitai bot commented Oct 30, 2025

Walkthrough

Restructures instructor assessment docs: renames and reorganizes auto-graded assessment sections, adds AI generation guidance and step-by-step authoring, expands secure-folder and file-organization security guidance, standardizes common configuration sections and wording, and updates images and examples.

Changes

Cohort / File(s) Summary
Assessment Navigation & Structure
source/instructors/authoring/assessments/add-assessment.rst, source/instructors/authoring/assessments/assessments.rst
Renamed "Auto-graded assessments" to "Auto‑Graded Assessments"; updated toctree (removed parameterized); added "How to Add a New Assessment" and "Auto‑Graded Assessment Types"; introduced "Common Assessment Configuration" with General, Metadata (Optional), and Files (Optional); adjusted headings, phrasing, and cross‑references.
Assessment Implementation & Configuration
source/instructors/authoring/assessments/advanced-code-test.rst, source/instructors/authoring/assessments/autograde-free-text.rst
Restructured setup steps (e.g., "Complete General"); standardized labels (e.g., "Partial Points"); reorganized Grading/Metadata/Files as optional blocks; added "Test Types" and per-tool standardized guidance; updated image references, example commands, and starter/example guidance.
AI-Based Assessment & Security
source/instructors/authoring/assessments/ai-assessment-generation.rst, source/instructors/authoring/assessments/assessment-security.rst
Added AI-generated assessment workflow and "How to Generate Assessment with AI" steps, expanded example prompts (Parson's, Fill-in-the-blanks, Standard Code Test, MCQ); replaced legacy security notes with explicit "File Organization", "Student Workspace Limitations", "The Secure Folder" sections and concrete implementation methods for ephemeral container mounting.
Minor Updates
source/instructors/authoring/assessments/delete-assessment.rst
Small inline code example update (example ID changed).

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~25 minutes

  • Verify cross-references between restructured files (add-assessment.rstassessments.rst) are intact.
  • Confirm referenced image filenames/paths in advanced-code-test.rst and other files exist and render.
  • Check security/secure-folder implementation wording against platform behavior (mounting, parameters, workspace limits).
  • Validate "Partial Points" preconditions (e.g., advanced code support) are accurate.

Possibly related PRs

  • added LLM-based rubric auto-grade #426 — Edits to add-assessment.rst and AI/LLM-based auto-generation content; likely overlaps with auto-generation wording and examples.
  • LTIUpdateandotherfixes #418 — Related documentation changes for assessment auto-generation and standard-code-test content; may affect consistency of AI generation docs.

Suggested reviewers

  • shajason
  • jairovelasquez

Pre-merge checks

❌ Failed checks (1 warning, 1 inconclusive)
Check name Status Explanation Resolution
Docstring Coverage ⚠️ Warning Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. You can run @coderabbitai generate docstrings to improve docstring coverage.
Title Check ❓ Inconclusive The title "assessment updates part 1" is vague and generic, similar to the "misc updates" example provided in the evaluation criteria. While it does reference "assessment" which is technically related to the changeset content, it fails to convey meaningful information about the nature of the updates. The PR contains substantial restructuring of documentation files, additions of new sections (like "AI-Generated Assessment Generation," "Common Assessment Configuration," and "File Organization"), reorganization of content, and terminology consistency improvements. A teammate scanning the repository history would not understand whether this PR involves bug fixes, new features, documentation reorganization, or content clarification based solely on this title. Consider revising the title to be more descriptive and specific about the primary changes. A stronger title might reflect the main objectives, such as "Restructure assessment documentation and add AI generation guidance" or "Reorganize assessment docs with common configuration sections and AI generation support." This would help reviewers and future developers quickly understand the scope and purpose of the changes without needing to review the full changeset.
✅ Passed checks (1 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 9

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (2)
source/instructors/authoring/assessments/ai-assessment-generation.rst (1)

53-69: Review example prompts for tone and consistency.

The example prompts are well-structured but have mixed tones and specificity levels:

  • "Multiple choice" example is brief and generic.
  • "Parson's Problem," "Fill in the Blanks," and "Standard Code Test" are much more detailed and prescriptive.

Consider adjusting the first example to match the detail level and format of the others for consistency:

 **Multiple choice**
 
-- Create a question about how to refactor the code below with multiple correct answers: (include code)
+- Create a multiple choice question about refactoring techniques with multiple correct answers. Include code samples demonstrating each option.
source/instructors/authoring/assessments/advanced-code-test.rst (1)

170-172: Inconsistent image formatting: missing :width: specification.

The pycodestyle image at line 170 lacks a :width: attribute, while the images at line 38 (Grading) and line 220 (Custom) both specify :width: 500px. For consistency across the document, add the width specification.

  .. image:: /img/guides/assessment_act_exec_pycodestyle.png
     :alt: Pycodestyle
+    :width: 500px
📜 Review details

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 7888f23 and 23ddaaf.

⛔ Files ignored due to path filters (5)
  • source/img/guides/ACTGradingScreen.png is excluded by !**/*.png, !**/*.png
  • source/img/guides/assessment_act_exec_custom.png is excluded by !**/*.png, !**/*.png
  • source/img/guides/assessment_undelete.png is excluded by !**/*.png, !**/*.png
  • source/img/guides/duplicate-assessment.png is excluded by !**/*.png, !**/*.png
  • source/img/guides/editassessmentbutton.png is excluded by !**/*.png, !**/*.png
📒 Files selected for processing (7)
  • source/instructors/authoring/assessments/add-assessment.rst (3 hunks)
  • source/instructors/authoring/assessments/advanced-code-test.rst (6 hunks)
  • source/instructors/authoring/assessments/ai-assessment-generation.rst (1 hunks)
  • source/instructors/authoring/assessments/assessment-security.rst (1 hunks)
  • source/instructors/authoring/assessments/assessments.rst (1 hunks)
  • source/instructors/authoring/assessments/autograde-free-text.rst (4 hunks)
  • source/instructors/authoring/assessments/delete-assessment.rst (1 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
**/*.rst

⚙️ CodeRabbit configuration file

**/*.rst: Review files for:

  • Consistent formatting (e.g., headings, lists, links).
  • Clear and concise language.
  • Correct grammar and spelling.
  • Proper use of rst syntax (e.g., avoid broken links or invalid code blocks).
  • Adherence to style guides (e.g., consistent tone, terminology).
    Suggest improvements to enhance readability and accessibility.
  • Make sure to find all improvements on the first pass.
    Go through the material multiple times before submitting comments.

Files:

  • source/instructors/authoring/assessments/assessments.rst
  • source/instructors/authoring/assessments/add-assessment.rst
  • source/instructors/authoring/assessments/delete-assessment.rst
  • source/instructors/authoring/assessments/assessment-security.rst
  • source/instructors/authoring/assessments/autograde-free-text.rst
  • source/instructors/authoring/assessments/ai-assessment-generation.rst
  • source/instructors/authoring/assessments/advanced-code-test.rst
🔇 Additional comments (14)
source/instructors/authoring/assessments/delete-assessment.rst (1)

27-27: LGTM!

The example code reference update is correct, and the Note block formatting is properly maintained.

source/instructors/authoring/assessments/ai-assessment-generation.rst (1)

48-48: Verify cross-reference syntax for layout.

The reference at line 48 uses :ref:layout; `` with a trailing semicolon inside the reference syntax. Confirm this is valid RST syntax; if the semicolon should appear outside the reference, adjust accordingly:

-.. important:: The generate assessment feature does not configure the page :ref:`layout; <layout>` you should specify the layout depending on how you want to present the information to the students.
+.. important:: The generate assessment feature does not configure the page :ref:`layout <layout>`; you should specify the layout depending on how you want to present the information to the students.
source/instructors/authoring/assessments/add-assessment.rst (2)

38-40: Verify cross-reference link target names match referenced content.

The introductory paragraph (lines 38-40) references multiple assessment types with cross-references like :ref:Multiple Choice `` and :ref:Parsons Puzzle `. Confirm that:

  1. The target names in angle brackets match the actual file reference labels (e.g., .. _multiple-choice: in the target file).
  2. The references link correctly across the documentation structure.

If documentation organization has changed, ensure all link targets are updated consistently.


58-72: LGTM!

The "Auto-Graded Assessment Types" section provides a clear, well-organized bulleted list of assessment options. The list is consistent with the earlier mention of supported AI-generated assessment types and serves as a good reference for users.

source/instructors/authoring/assessments/assessments.rst (2)

6-21: LGTM!

The new "Assessment Topics" section is clearly structured and provides logical navigation for users. The bulleted list of cross-referenced topics is consistent with the documentation's organization and uses proper RST syntax.


23-57: LGTM!

The new "Common Assessment Configuration" section is well-organized with clear subsection hierarchy (General Settings, Metadata, Files). The use of images with descriptive alt text, bullet points, and inline formatting (bold for field names) enhances readability. The content is concise and informative, and the subsection underlines are consistent throughout.

source/instructors/authoring/assessments/autograde-free-text.rst (5)

10-12: LGTM!

The cross-reference note at lines 10-12 is well-integrated and provides helpful navigation to related sections. The phrasing is clear and the reference syntax is correct.


21-21: LGTM!

The updated Note block effectively references the Assessment Security documentation and clarifies the security benefits of the .guides/secure folder. The explanation is clear and actionable.


38-49: LGTM!

The Preview Type options have been properly converted from plaintext to a well-formatted RST bordered table. The table clearly presents the three options (Plaintext, Plaintext + LaTeX, Markdown + LaTeX) with concise descriptions. The formatting is consistent with RST conventions.


56-59: LGTM!

The optional section labels "(Optional) Complete Metadata" and "(Optional) Complete Files" at lines 56 and 58 are clear and consistent. This labeling pattern helps users understand which sections are required versus optional.


63-64: Minor improvement: Streamline section title punctuation.

The section title uses a period after the main heading at line 63-64: "Example Scripts for Free-Text Auto-Grade with All or Nothing Scoring." and "............................................................"

RST section titles should not include trailing periods. Remove the period for consistency with standard RST conventions:

-Example Scripts for Free-Text Auto-Grade with All or Nothing Scoring
-.....................................................................
+Example Scripts for Free-Text Auto-Grade with All or Nothing Scoring
+.....................................................................

Likely an incorrect or invalid review comment.

source/instructors/authoring/assessments/advanced-code-test.rst (3)

43-43: Inconsistent capitalization for partial-points toggle/field names.

The document uses mixed capitalization when referring to partial-points functionality:

  • Line 43: Partial Points (capitalized words)
  • Lines 97, 109: ALLOW PARTIAL POINTS (all caps)
  • Line 188: ALLOW PARTIAL POINTS (all caps)

Standardize the terminology throughout. If ALLOW PARTIAL POINTS is the actual UI field name, it should be consistently used; otherwise, use sentence case (e.g., "Partial Points") for descriptive text. Verify the correct name from the UI and apply uniformly.

Can you confirm the official UI field name for this toggle across the documentation? This will help ensure consistent terminology.

Also applies to: 97-97, 109-109, 188-188


56-64: "See a Working Example" section provides clear, actionable guidance.

The new subsection effectively guides users to Starter Packs and reference materials. The structure and formatting are clear, and the references are well-organized by language/framework.


182-198: UnitTest configuration section is well-structured and comprehensive.

The new "Configuration" and "Optional Configurations" subsections clearly separate required setup steps from advanced options. The numbered list and bullet formatting are consistent and easy to follow. Cross-reference to the Starter Pack is a helpful addition.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 3

♻️ Duplicate comments (3)
source/instructors/authoring/assessments/ai-assessment-generation.rst (1)

24-24: Remove redundant restriction statement from procedural step.

The restriction that "not all assessments can be AI-generated" is stated in the Note block (line 24) and unnecessarily repeated in step 3 (line 39). This duplication weakens the procedural clarity. Remove the redundant sentence from step 3 and retain it only in the Note.

 3. The Generation Prompt will open, press **Generate Using AI** to preview the generated assessment. Not all assessments can be AI-generated.
+3. The Generation Prompt will open, press **Generate Using AI** to preview the generated assessment.

Also applies to: 39-39

source/instructors/authoring/assessments/assessment-security.rst (2)

18-19: Adjust heading underline length to match text.

The underline for "Student Workspace Limitations" is one character short. RST requires the underline to match the heading length exactly.

 Student Workspace Limitations
-~~~~~~~~~~~~~~~~~~~~~~~~~~~
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~

87-88: Adjust heading underline length to match text.

The underline for "Important Limitations" has one extra character.

 Important Limitations
-~~~~~~~~~~~~~~~~~~~~~
+~~~~~~~~~~~~~~~~~~~~
📜 Review details

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 23ddaaf and 78b7c86.

📒 Files selected for processing (5)
  • source/instructors/authoring/assessments/add-assessment.rst (3 hunks)
  • source/instructors/authoring/assessments/advanced-code-test.rst (6 hunks)
  • source/instructors/authoring/assessments/ai-assessment-generation.rst (1 hunks)
  • source/instructors/authoring/assessments/assessment-security.rst (1 hunks)
  • source/instructors/authoring/assessments/autograde-free-text.rst (4 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
**/*.rst

⚙️ CodeRabbit configuration file

**/*.rst: Review files for:

  • Consistent formatting (e.g., headings, lists, links).
  • Clear and concise language.
  • Correct grammar and spelling.
  • Proper use of rst syntax (e.g., avoid broken links or invalid code blocks).
  • Adherence to style guides (e.g., consistent tone, terminology).
    Suggest improvements to enhance readability and accessibility.
  • Make sure to find all improvements on the first pass.
    Go through the material multiple times before submitting comments.

Files:

  • source/instructors/authoring/assessments/autograde-free-text.rst
  • source/instructors/authoring/assessments/add-assessment.rst
  • source/instructors/authoring/assessments/assessment-security.rst
  • source/instructors/authoring/assessments/advanced-code-test.rst
  • source/instructors/authoring/assessments/ai-assessment-generation.rst
🔇 Additional comments (6)
source/instructors/authoring/assessments/advanced-code-test.rst (1)

1-230: Restructuring and past issues resolved effectively.

The grammar corrections ("more than" vs "more then"), capitalization alignment ("SOURCE PATH"), and secure folder path consistency have been properly applied throughout. The new "Test Types" section provides clear organization of framework-specific guidance.

source/instructors/authoring/assessments/add-assessment.rst (1)

1-72: Heading and structure alignment resolved.

The capitalization consistency between the main heading and toctree caption has been properly updated. The new "How to Add a New Assessment" section provides clear step-by-step guidance, and the "Auto-Graded Assessment Types" section offers well-organized cross-references.

source/instructors/authoring/assessments/autograde-free-text.rst (1)

36-49: Well-structured table for Preview Type options.

The table format (lines 38–49) clearly presents the three preview options with their descriptions using proper reStructuredText table syntax. This improves readability compared to narrative text.

source/instructors/authoring/assessments/assessment-security.rst (3)

110-111: Adjust heading underline length to match text.

The underline for "Implementation Methods" has one extra character.

 Implementation Methods
-~~~~~~~~~~~~~~~~~~~~~~
+~~~~~~~~~~~~~~~~~~~~~

Likely an incorrect or invalid review comment.


39-40: Adjust heading underline length to match text.

The underline for "Updating Published Assignments" is one character short.

 Updating Published Assignments
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Likely an incorrect or invalid review comment.


77-78: Adjust heading underline length to match text.

The underline for "How It Works" has one extra character.

 How It Works
-~~~~~~~~~~~~
+~~~~~~~~~~~

Likely an incorrect or invalid review comment.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

📜 Review details

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 78b7c86 and b6b2dd0.

📒 Files selected for processing (2)
  • source/instructors/authoring/assessments/ai-assessment-generation.rst (1 hunks)
  • source/instructors/authoring/assessments/autograde-free-text.rst (3 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
**/*.rst

⚙️ CodeRabbit configuration file

**/*.rst: Review files for:

  • Consistent formatting (e.g., headings, lists, links).
  • Clear and concise language.
  • Correct grammar and spelling.
  • Proper use of rst syntax (e.g., avoid broken links or invalid code blocks).
  • Adherence to style guides (e.g., consistent tone, terminology).
    Suggest improvements to enhance readability and accessibility.
  • Make sure to find all improvements on the first pass.
    Go through the material multiple times before submitting comments.

Files:

  • source/instructors/authoring/assessments/autograde-free-text.rst
  • source/instructors/authoring/assessments/ai-assessment-generation.rst
🔇 Additional comments (2)
source/instructors/authoring/assessments/autograde-free-text.rst (2)

65-66: Fix heading underline length to match text.

The underline for "Example Scripts for Free-Text Auto-Grade with All or Nothing Scoring" is too short. The heading is 68 characters, but the underline appears to be only approximately 64 tildes. Per RST conventions, the underline must exactly match the heading length.

 Example Scripts for Free-Text Auto-Grade with All or Nothing Scoring
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

10-60: Excellent restructuring of setup instructions.

The reorganized setup steps with clearer formatting, enhanced cross-references (linking Assessments, Metadata, and Files), and improved field descriptions make the documentation more accessible. The new bordered table for Preview Type options (lines 39–50) is well-formatted and easier to parse than inline text.

@LolaValente LolaValente merged commit 23af792 into master Oct 30, 2025
1 check passed
@LolaValente LolaValente deleted the AssessmentsUpdate branch October 30, 2025 21:11
This was referenced Oct 31, 2025
@coderabbitai coderabbitai bot mentioned this pull request Nov 17, 2025
@coderabbitai coderabbitai bot mentioned this pull request Jan 13, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants