SóProvas

ID
2649325
Banca
CESPE / CEBRASPE
Órgão
STJ
Ano
2018
Provas
Disciplina
Engenharia de Software
Assuntos

Julgue o item a seguir, acerca de eMAG, sistemas de controle de versão e SonarQube.


Uma issue gerada pelo SonarQube com severidade CRITICA requer a imediata correção do código.

Alternativas
Comentários

  • Issue com severidade CRITICA deve ser revisada.

    Issue com severidade BLOCKER deve ser corrigida.


    BLOCKER

    Bug with a high probability to impact the behavior of the application in production: memory leak, unclosed JDBC connection, .... The code MUST be immediately fixed.

    CRITICAL

    Either a bug with a low probability to impact the behavior of the application in production or an issue which represents a security flaw: empty catch block, SQL injection, ... The code MUST be immediately reviewed.


    Fonte: https://docs.sonarqube.org/display/SONAR/Issues

  • Complementando de forma intuitiva:

    C

    BLOCKER

    R

    R

    I

    D

    A

    Issue com severidade CRÍTICA deve ser Revisada.

    Issue com severidade BLOCKER deve ser corrigida.

  • Each issue has one of five severities:

    1. BLOCKER
    2. Bug with a high probability to impact the behavior of the application in production: memory leak, unclosed JDBC connection, .... The code MUST be fixed immediately.
    3. CRITICAL
    4. Either a bug with a low probability to impact the behavior of the application in production or an issue which represents a security flaw: empty catch block, SQL injection, ... The code MUST be immediately reviewed.
    5. MAJOR
    6. Quality flaw which can highly impact the developer productivity: uncovered piece of code, duplicated blocks, unused parameters, ...
    7. MINOR
    8. Quality flaw which can slightly impact the developer productivity: lines should not be too long, "switch" statements should have at least 3 cases, ...
    9. INFO
    10. Neither a bug nor a quality flaw, just a finding.