Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

E1971. OSS project Finklestein: Instructors & Institutions #1506

Closed
wants to merge 28 commits into from

Conversation

YongjianZhu
Copy link

Please put the title of your pull request in the following format: Project ID. Name
for example, [Project id/Independent study/Issue fix/...]. project name, eg., E904. Integrating courses and assignments on Expertiza with Moodle

We suggest you include below information in your pull request:

  • A description of the changes proposed in the pull request.
  • @mentions of the person or team responsible for reviewing proposed changes.

@expertiza-bot
Copy link
Contributor

expertiza-bot commented Oct 9, 2019

1 Message
💬 Thanks for the pull request, and welcome! 🎉 The Expertiza team is excited to review your changes, and you should hear from us soon.

This repository is being automatically checked for code-quality issues using Code Climate.
You can see results for this analysis in the PR status below. Newly introduced issues should be fixed before a pull request is considered ready to review.

Also, please spend some time looking at the instructions at the top of your course project writeup.
If you have any questions, please send email to expertiza-support@lists.ncsu.edu.

3 Warnings
⚠️ You changed MARKDOWN (*.md) documents; please double-check whether it is necessary to do so.
Alternatively, you can insert project-related content in the description field of the pull request.
⚠️ You should commit changes to the DB schema (db/schema.rb) only if you have created new DB migrations.
Please double check your code. If you did not aim to change the DB, please revert the DB schema changes.
⚠️ In your tests, there are many expectations of elements on pages, which is good.
To avoid shallow tests – tests concentrating on irrelevant, unlikely-to-fail conditions – please write more expectations to validate other things, such as database records, dynamically generated contents.
One or more of your tests do not have expectations or you commented out some expectations.
To avoid shallow tests – tests concentrating on irrelevant, unlikely-to-fail conditions – please write at least one expectation for each test and do not comment out expectations.
There are one or more skipped/pending/focused test cases in your pull request. Please fix them.
The should syntax is deprecated in RSpec 3. Please use expect syntax instead.
Even in test descriptions, please avoid using should.
There are code changes, but no corresponding tests.
Please include tests if this PR introduces any modifications in behavior.

Generated by expertiza-bot

@coveralls
Copy link

Coverage Status

Coverage decreased (-13.7%) to 16.818% when pulling 3505823 on YongjianZhu:dev into 28eb0da on expertiza:beta.

@coveralls
Copy link

coveralls commented Oct 9, 2019

Coverage Status

Coverage decreased (-6.1%) to 24.364% when pulling 4250c4f on YongjianZhu:dev into 28eb0da on expertiza:beta.

@expertiza-travisci-bot
Copy link

expertiza-travisci-bot commented Oct 9, 2019

Travis tests have failed

Hey @YongjianZhu,
Please click the following black triangle (▶) in order to see the detailed information.
It'll be awesome if you fix what's wrong and commit the changes.

Feature Tests:

Detailed Information
[Coveralls] Set up the SimpleCov formatter.
[Coveralls] Using SimpleCov's 'rails' settings.

Randomized with seed 61884
....................................********...F............................*........**.**...***************...........................*****..........********.**........*...........*............*......................

Pending: (Failures listed here are expected and do not affect your suite's status)

  1) Team Creation one student who signup for a topic should send an inviatation to the other student who has no topic is not able to form team on rejecting
     # Temporarily skipped with xdescribe
     # ./spec/features/team_creation_spec.rb:63

  2) Team Creation one student who signup for a topic should send an inviatation to the other student who has no topic is able to accept the invitation and form team
     # Temporarily skipped with xdescribe
     # ./spec/features/team_creation_spec.rb:57

  3) Team Creation one student should send an invitation to other student and both does not have topics Student should accept other students invitation and both does not have a topic
     # Temporarily skipped with xdescribe
     # ./spec/features/team_creation_spec.rb:181

  4) Team Creation one student should send an invitation to other student and both does not have topics Student should reject the other students invitaton and both dont have a topic
     # Temporarily skipped with xdescribe
     # ./spec/features/team_creation_spec.rb:187

  5) Team Creation one student should send an invitation to other student who has a topic signed up for Student should accept the invitation sent by other student who has a topic
     # Temporarily skipped with xdescribe
     # ./spec/features/team_creation_spec.rb:237

  6) Team Creation one student should send an invitation to other student who has a topic signed up for Student should reject the inviattion sent by the other student who has a topic
     # Temporarily skipped with xdescribe
     # ./spec/features/team_creation_spec.rb:243

  7) Team Creation one student who has a topic sends an invitation to other student who also has a topic Student should aceept the invitation sent by the other student and both have topics
     # Temporarily skipped with xdescribe
     # ./spec/features/team_creation_spec.rb:122

  8) Team Creation one student who has a topic sends an invitation to other student who also has a topic student should reject the invitation sent by the other student and both gave topics
     # Temporarily skipped with xdescribe
     # ./spec/features/team_creation_spec.rb:128

  9) assignment submisstion test should not submit invalid link
     # the error depends on the dns server. For spectrum network provider, invalid url will redirect to http://www.dnsrsearch.com
     # ./spec/features/assignment_submission_spec.rb:39

  10) review mapping show error when assign both 2
     # skip test on automated review mapping, too time consuming
     # ./spec/features/review_mapping_spec.rb:83

  11) review mapping show error when assign both 0
     # skip test on automated review mapping, too time consuming
     # ./spec/features/review_mapping_spec.rb:89

  12) review mapping calculate review mapping from given review number per student
     # skip test on automated review mapping, too time consuming
     # ./spec/features/review_mapping_spec.rb:95

  13) review mapping calculate reviewmapping from given review number per submission
     # skip test on automated review mapping, too time consuming
     # ./spec/features/review_mapping_spec.rb:102

  14) badge system in assignments#edit page has a tab named 'Badges'
     # Not yet implemented
     # ./spec/features/badge_system_spec.rb:13

  15) badge system in assignments#edit page when switching to 'Badges' tab allows instructor to change the thresholds of two badges (by default is 95) and save thresholds to DB
     # Not yet implemented
     # ./spec/features/badge_system_spec.rb:16

  16) badge system when a student receives a very high average teammate review grade (higher than 95 by default) assigns the 'Good teammate' badge to this student on student_task#list page
     # Not yet implemented
     # ./spec/features/badge_system_spec.rb:21

  17) badge system when a student receives a very high review grades assigned by teaching staff (higher than 95 by default) assigns the 'Good reviewer' badge to this student on student_task#list page
     # Not yet implemented
     # ./spec/features/badge_system_spec.rb:25

  18) badge system on participants#list page allows instructor to view badges assignment statuses of all participants
     # Not yet implemented
     # ./spec/features/badge_system_spec.rb:29

  19) team invitation when current assignment is a team-based assignment with topics on student_teams#view page (student end) shows a list of students who do not have a team and team owner can invite these students by clicking the 'invite' buttons
     # Not yet implemented
     # ./spec/features/team_invitation_spec.rb:44

  20) team invitation when current assignment is a team-based assignment with topics on student_teams#view page (student end) when invitee accepting the invitation when the team is already full makes team members remain the same as before
     # Not yet implemented
     # ./spec/features/team_invitation_spec.rb:56

  21) team invitation when current assignment is a team-based assignment with topics on student_teams#view page (student end) when invitee accepting the invitation when the team is not full makes invitee joins the team
     # Not yet implemented
     # ./spec/features/team_invitation_spec.rb:52

  22) team invitation when current assignment is a team-based assignment with topics on student_teams#view page (student end) when invitee declining the invitation makes team members remain the same as before
     # Not yet implemented
     # ./spec/features/team_invitation_spec.rb:47

  23) team invitation when current assignment is a team-based assignment with topics when a student access studet_task#list page of this assignment contains 'Your team' link on the page
     # Not yet implemented
     # ./spec/features/team_invitation_spec.rb:14

  24) team invitation when current assignment is a team-based assignment with topics advertisement feature when team owner declining the invitation makes team members remain the same as before
     # Not yet implemented
     # ./spec/features/team_invitation_spec.rb:29

  25) team invitation when current assignment is a team-based assignment with topics advertisement feature when team owner accepting the invitation when the team is already full makes team members remain the same as before
     # Not yet implemented
     # ./spec/features/team_invitation_spec.rb:38

  26) team invitation when current assignment is a team-based assignment with topics advertisement feature when team owner accepting the invitation when the team is not full makes requester joins the team
     # Not yet implemented
     # ./spec/features/team_invitation_spec.rb:34

  27) team invitation when current assignment is a team-based assignment with topics on teams#list page (instructor end) shows a list of students who do not have a team
     # Not yet implemented
     # ./spec/features/team_invitation_spec.rb:62

  28) team invitation when current assignment is not a team-based assignment when a student access studet_task#list page of this assignment does not contain 'Your team' link on the page
     # Not yet implemented
     # ./spec/features/team_invitation_spec.rb:68

  29) calibration in assignments#edit page has a checkbox with title 'Calibration for training?' on 'General' tab
     # Not yet implemented
     # ./spec/features/calibration_spec.rb:13

  30) calibration in assignments#edit page when clicking 'Calibration for training?' checkbox and clicking 'save' button 'Calibration' due date works correctly
     # Not yet implemented
     # ./spec/features/calibration_spec.rb:17

  31) calibration when current assignment is in calibration stage calibration feature works correctly
     # Not yet implemented
     # ./spec/features/calibration_spec.rb:27

  32) calibration when current assignment is in review stage excludes calibration reviews from outstanding review restriction and total review restriction
     # Not yet implemented
     # ./spec/features/calibration_spec.rb:39

  33) calibration when current assignment is in review stage shows 'Review 1, 2, 3...' instead of 'Calibration review 1, 2, 3...' on student_review#list page
     # Not yet implemented
     # ./spec/features/calibration_spec.rb:41

  34) timestamps for student's submissions when current assignment is in submission stage after current participant has submitted a hyperlink displays hyperlinks with its timestamps
     # Not yet implemented
     # ./spec/features/timestamps_for_students_submissions_spec.rb:18

  35) timestamps for student's submissions when current assignment is in submission stage when current participant does not submit anything yet displays due dates of current assignment in student_task#list page
     # Not yet implemented
     # ./spec/features/timestamps_for_students_submissions_spec.rb:14

  36) timestamps for student's submissions when current assignment is in submission stage after current participant has uploaded a file displays file names with its timestamps
     # Not yet implemented
     # ./spec/features/timestamps_for_students_submissions_spec.rb:23

  37) timestamps for student's submissions when current assignment (with multiple review round) is in review stage after current participant finishes an author feedback displays a link named 'feedback' with its timestamps (you could redirect to that feedback by clicking the link)
     # Not yet implemented
     # ./spec/features/timestamps_for_students_submissions_spec.rb:58

  38) timestamps for student's submissions when current assignment (with multiple review round) is in review stage after current participant reviews other's work in round 1 displays a link named 'review' with its round number (1) and timestamps (you could redirect to that review by clicking the link)
     # Not yet implemented
     # ./spec/features/timestamps_for_students_submissions_spec.rb:45

  39) timestamps for student's submissions when current assignment (with multiple review round) is in review stage after current participant reviews other's work in round 2 displays a link named 'review' with its round number (2) and timestamps (you could redirect to that review by clicking the link)
     # Not yet implemented
     # ./spec/features/timestamps_for_students_submissions_spec.rb:51

  40) timestamps for student's submissions when current assignment (with single review round) is in review stage after current participant reviews other's work displays a link named 'review' with its timestamps (you could redirect to that review by clicking the link) 
     # Not yet implemented
     # ./spec/features/timestamps_for_students_submissions_spec.rb:30

  41) timestamps for student's submissions when current assignment (with single review round) is in review stage after current participant finishes an author feedback displays a link named 'feedback' with its timestamps (you could redirect to that feedback by clicking the link)
     # Not yet implemented
     # ./spec/features/timestamps_for_students_submissions_spec.rb:36

  42) expert review when current assignment with single review round supports expert peer-review expert review feature works correctly
     # Not yet implemented
     # ./spec/features/expert_review_spec.rb:14

  43) expert review when current assignment with vary-rubric-by-round supports expert peer-review expert review feature works correctly
     # Not yet implemented
     # ./spec/features/expert_review_spec.rb:28

  44) assignment function Due dates tab Able to create a new penalty policy
     # Temporarily skipped with xit
     # ./spec/features/assignment_creation_spec.rb:661

  45) assignment function creation page is able to create with staggered deadline
     # skip test on staggered deadline temporarily
     # ./spec/features/assignment_creation_spec.rb:122

  46) assignment function review strategy tab sets number of reviews by each student
      # review section not yet completed
      Failure/Error: check 'num_reviews_student'
      
      Capybara::ElementNotFound:
        Unable to find visible checkbox "num_reviews_student" that is not disabled
      # ./spec/features/assignment_creation_spec.rb:621:in `block (3 levels) in <top (required)>'

Failures:

  1) Assignment Topic Suggestion Test topic_suggestion  student2064 hold suggest topic and suggest a new one and student2065 enroll on waitlist of suggested topic
     Failure/Error:
       child_nodes.each do |node|
         initialize_fnode_update_children(params, node, tmp_res)
       end
     
     NoMethodError:
       undefined method `each' for "":String
     # ./app/controllers/tree_display_controller.rb:209:in `children_node_ng'
     # ./config/diagnostic.rb:11:in `call'
     # ------------------
     # --- Caused by: ---
     # Capybara::CapybaraError:
     #   Your application server raised an error - It has been raised in your test code because Capybara.raise_server_errors == true
     #   ./spec/features/topic_suggestion_spec.rb:115:in `block (3 levels) in <top (required)>'

Finished in 7 minutes 32 seconds (files took 4.68 seconds to load)
217 examples, 1 failure, 46 pending

Failed examples:

rspec ./spec/features/topic_suggestion_spec.rb:55 # Assignment Topic Suggestion Test topic_suggestion  student2064 hold suggest topic and suggest a new one and student2065 enroll on waitlist of suggested topic

Randomized with seed 61884

Coverage report generated for RSpec to /home/travis/build/expertiza/expertiza/coverage. 4244 / 14358 LOC (29.56%) covered.
[Coveralls] Submitting to https://coveralls.io/api/v1
[Coveralls] Job #8378.1
[Coveralls] https://coveralls.io/jobs/55695147
Coverage is at 29.56%.
Coverage report sent to Coveralls.

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.

None yet

6 participants