~/talk

Scala Quality assurance

Talkat Scala.IO 2014 · 2014-10-23..10-24· [developer-experience]
links:none on file
slides:none on file

Claim: automated QA improves team safety by enforcing measurable coverage and static checks. Tools and outcomes: Scoverage (statement-level coverage) replaces SCCT for Scala, Jacoco via scoverage-sbt or jacoco-sbt for bytecode cases, GitLab CI Runner runs SBT and frontend Karma builds, results fed into Sonar for centralized dashboards. Workflow examples: API JSON generation for offline frontend dev, CI-triggered builds on pull requests, experiments with Magenta/RiffRaff for deploys; statement and branch metrics differ noticeably.

AI-written summary · about

  1. 0:00Introduction to Scala quality assurance
  2. 2:05What is QA in software
  3. 4:00CI tools for Scala
  4. 5:27Code coverage techniques
  5. 9:23Coverage tools for Scala
  6. 16:32Static code analysis
  7. 17:37SonarQube for metrics
  8. 19:49Team QA workflow
  9. 21:41GitHub/GitLab CI
  10. 23:09CI deployment automation
  11. 24:35Q&A on metrics
  12. 27:48Coverage tools impact
  13. 29:22Setting up SonarQube for Scala projects
  14. 30:28Closing remarks
~/search
type to search 6,249 conferences, 138,987 speakers and 185,172 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.