Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • T ticket
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1,809
    • Issues 1,809
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Administrator
  • ticket
  • Issues
  • #80

Closed
Open
Created Jan 04, 2022 by Administrator@rootMaintainer

TestCases should contain tests

Created by: armorcodegithubqa[bot]

There's no point in having a JUnit TestCase without any test methods. Similarly, you shouldn't have a file in the tests directorynamed *Test, *Tests, or *TestCase, but no tests in the file. Doing either of these things may lead someone tothink that uncovered classes have been tested.

This rule raises an issue when files in the test directory are named *Test, *Tests, or *TestCase orimplement TestCase but don't contain any tests.

Supported frameworks:

  • JUnit3
  • JUnit4
  • JUnit5
  • TestNG
  • Zohhak
  • ArchUnit
  • Pact

File Path: webgoat-lessons/sql-injection/src/test/java/org/owasp/webgoat/sql_injection/SqlLessonTest.java:33

Mitigation: Add some tests to this class.

https://qa.armorcode.ai/#/findings/5439750

Assignee
Assign to
Time tracking