mikepenz/action-junit-report

Issues

• Have tests grouped by suite in summary

  #1080 opened 2 months ago by guusdk
  9

• XML parsing failures do not fail the action and can hide failing tests

  #1189 opened 2 months ago by aconti-ns1
  3

• Only generate summary

  #1219 opened 2 months ago by stephanos
  0

• Unexpected input(s) 'comment'

  #1186 opened 2 months ago by kjetilk-kontali
  7

• Trying to understand how glob.create is used in resolvePath

  #1177 opened 2 months ago by enobrev
  4

• Show raw output for passed test

  #1162 opened 2 months ago by amanank
  1

• Testem.js xunit report browser name as classname property parsed incorrectly

  #1065 opened 9 months ago by raido
  1

• Option to explicitly fail check run

  #994 opened 2 months ago by pavetok
  9

• Question - works with newer gradle?

  #1190 opened 2 months ago by flozano
  5

• No report/summary generated when there are no passing tests and set to require passing tests

  #1215 opened 2 months ago by daantimmer
  1

• PR comment behavior

  #1178 opened 4 months ago by janniclas
  0

• Suggestion: provide info on setting --max_old_space_size

  #1170 opened 4 months ago by arcuri82
  3

• Add summary as PR comment

  #1166 opened 4 months ago by Cavaler
  1

• Question on annotations when the action is applied in a resuable workflow

  #1153 opened 4 months ago by watermarkhu
  2

• Failed to create checks using the provided token.

  #1126 opened 5 months ago by saisanthoshkonduri
  5

• Multiple XML file locations

  #1140 opened 6 months ago by kajoshi0117
  2

• Duplicate tests?

  #1136 opened 6 months ago by swwol
  3

• Annotations not being produced

  #1121 opened 6 months ago by mendezj-eikontx
  2

• JUnit task reporting only goes 2 levels deep

  #1086 opened 6 months ago by KlemenDEV
  8

• Doesn't include errors

  #1005 opened 6 months ago by sheikhasim
  4

• Option to report flaky tests

  #1108 opened 6 months ago by knsonier
  0

• Annotation: message color

  #1094 opened 6 months ago by hikouki-gumo
  4

• Nullpointer in Node.js

  #1109 opened 6 months ago by guntermartens
  7

• check_name failed to report

  #1089 opened 8 months ago by hikoukii-gumoo
  0

• Node.js 16 deprecation warning

  #1093 opened 8 months ago by mendezj-eikontx
  1

• Annotations not being added to files when there are more than 50 failures

  #1063 opened 8 months ago by nfelt14
  7

• Support including message/stack traces in detailed summary report

  #1039 opened 9 months ago by raido
  3

• Error: ❌ No test results found for JUnit Test Report — but `junit.xml` looks reasonable to me

  #1051 opened 10 months ago by aviflax
  7

• missing mypy detail when annotate_only=true

  #1049 opened 10 months ago by Alex-ley-scrub
  4

• Check Run Not Created when update_check: true

  #927 opened 10 months ago by ShahroZafar
  2

• Support ESLint or Jest junit reports

  #1023 opened 10 months ago by villelahdenvuo
  6

• Skipping all Annotations

  #1020 opened a year ago by janbernhardt
  14

• Annotation truncates failure output/callstack

  #1006 opened a year ago by stackptr
  6

• Error: Converting circular structure to JSON

  #952 opened a year ago by arcuri82
  9

• Invalid character entity when using with dastardly

  #943 opened a year ago by JonLittleIT
  6

• act error: Error: The runs.using key in action.yml must be one of: [composite docker node12 node16], got node20

  #942 opened a year ago by renepyo
  4

• support "ignored" attribute

  #761 opened a year ago by garfieldnate
  5

• Failed tests are not shown in Annotations

  #904 opened a year ago by GitHubVadym
  9

• Skipped tests are show as passed when included_passed set to true

  #844 opened a year ago by gokhan-oner
  3

• Out of memory error on large project

  #880 opened 2 years ago by mumrah
  14

• Documentation for Maven Surefire

  #866 opened 2 years ago by arcuri82
  2

• action using deprecate 'set-output' command

  #854 opened 2 years ago by zibenua
  2

• Test failures not correctly recognized

  #847 opened 2 years ago by novoj
  8

• Editor points out that github_token is required

  #830 opened 2 years ago by mas0061
  1

• require_tests flag is not working

  #802 opened 2 years ago by fjbenitog
  5

• Test report stopped working without change

  #798 opened 2 years ago by marcheyer
  8

• Weird behavior with multiple `report_paths` and failures not being processed

  #794 opened 2 years ago by tiagobento
  4

• Different line number representation (xunit)

  #779 opened 2 years ago by KD-7
  3

• Source of file and line attributes

  #772 opened 2 years ago by alandefreitas
  5

• Option to not parse the annotations if number of failures is high

  #760 opened 2 years ago by ilyadh
  1