Scala Quality assurance
summary
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
chapters (14)
- 0:00Introduction to Scala quality assurance
- 2:05What is QA in software
- 4:00CI tools for Scala
- 5:27Code coverage techniques
- 9:23Coverage tools for Scala
- 16:32Static code analysis
- 17:37SonarQube for metrics
- 19:49Team QA workflow
- 21:41GitHub/GitLab CI
- 23:09CI deployment automation
- 24:35Q&A on metrics
- 27:48Coverage tools impact
- 29:22Setting up SonarQube for Scala projects
- 30:28Closing remarks
related talks
49mBuilding Safe, More Testable Scala Production Systems
51mQuality Assurance vs. Testing
46mCode coverage MythBusters
51mAutomate More Code With Scalameta
34mAutotest Coverage Visualization
46mThe Essence of Testing
55mZen and the Art of Code Life Cycle Maintenance
14mThinking of Quality as developer productivity tool
