import { createServiceTester } from '../tester.js'
import { codacyGrade } from './codacy-helpers.js'
export const t = await createServiceTester()

// https://app.codacy.com/gh/NicolasCARPi/jquery_jeditable/dashboard
// https://github.com/NicolasCARPi/jquery_jeditable
t.create('Code quality')
  .get('/0cb32ce695b743d68257021455330c66.json')
  .expectBadge({
    label: 'code quality',
    message: codacyGrade,
  })

t.create('Code quality on branch')
  .get('/0cb32ce695b743d68257021455330c66/master.json')
  .expectBadge({
    label: 'code quality',
    message: codacyGrade,
  })

t.create('Code quality (package not found)')
  .get('/00000000000000000000000000000000/master.json')
  .expectBadge({
    label: 'code quality',
    message: 'project or branch not found',
  })

// This is a known bug. The badge endpoint for a nonexistent branch returns
// the same result. It seems possible the branch specification isn't being
// considered at all.
// e.g.
// https://api.codacy.com/project/badge/grade/e27821fb6289410b8f58338c7e0bc686
// https://api.codacy.com/project/badge/grade/e27821fb6289410b8f58338c7e0bc686?branch=foo
// t.create('Code quality on branch (branch not found)')
//   .get('/grade/e27821fb6289410b8f58338c7e0bc686/not-a-branch.json')
//   .expectBadge({
//       label: 'code quality',
//       message: 'project or branch not found',
//   })