Quality Management
34 items tagged with "quality-management"
Standards7
ISO/IEC 9075:1992 (SQL-92)
Understanding ISO/IEC standards is vital for successful software migrations. By adhering to these guidelines, teams can mitigate risks, ensure compliance, and enhance stakeholder confidence. This comprehensive guide outlines the key requirements, practical steps for compliance, and tools to support your migration efforts.
ISO/IEC 27001:2022
Adhering to ISO/IEC standards is crucial for successful software migrations, as these standards ensure quality, security, and interoperability. By understanding compliance requirements and implementing best practices, teams can mitigate risks and foster stakeholder trust during the transition process.
ISO 9001:2015
Understanding and adhering to ISO standards is essential for successful software migrations. These standards provide a framework that helps organizations mitigate risks, enhance quality, and ensure regulatory compliance. By following key requirements and utilizing appropriate tools, teams can navigate the complexities of migration projects with confidence and clarity.
ISO 9126 (Quality Model – Superseded)
Adhering to ISO standards during software migrations is crucial for ensuring quality, security, and stakeholder trust. By implementing structured processes, conducting risk assessments, and utilizing effective tools, teams can navigate migration complexities while maintaining compliance and enhancing project outcomes.
PDF 1.7 (ISO 32000-1)
Understanding ISO standards is crucial for ensuring compliance, quality, and consistency in software migration projects. By following best practices and utilizing appropriate tools, teams can effectively manage risks and maintain stakeholder confidence throughout the migration process.
ISO/IEC 40500:2012 (WCAG 2.0)
Adhering to ISO/IEC standards during software migrations is essential for ensuring quality, risk management, and regulatory compliance. By following best practices and utilizing the right tools, teams can effectively navigate the challenges of migration projects and maintain stakeholder confidence.
ISO 15926 Part 2
ISO standards provide a vital framework for ensuring quality, security, and efficiency in software migrations. By adhering to these standards, teams can mitigate risks, enhance stakeholder confidence, and streamline their migration processes, ultimately leading to more successful outcomes.
Anti-Patterns15
Shotgun Surgery
Making a single change requires modifications across many different classes or modules
Magic Numbers
Unexplained numeric literals embedded in code, hiding their meaning and duplicating values that must change together.
Copy-Paste Programming
Duplicating blocks of code instead of factoring out shared logic, so every fix and change must be repeated across each copy, and some are missed.
Hardcoding
Embedding values that should be configurable, such as URLs, paths, credentials, and limits, directly in source, forcing code changes to adapt.
Redundant Comments
Comments that merely restate what the code already says, adding noise, drifting out of date, and masking the absence of self-explanatory code.
Rubber-Stamp Code Reviews
Approving pull requests without meaningful inspection, performing the ceremony of code review while providing none of its protective value.
Ice-Cream Cone (Inverted Test Pyramid)
A test suite dominated by slow manual and end-to-end tests with few unit tests, making feedback slow, brittle, and expensive to maintain.
Flaky Tests
Tests that pass and fail non-deterministically without code changes, eroding trust in the suite and masking real regressions.
Testing Implementation Details
Tests coupled to private internals rather than observable behavior, so harmless refactors break them and real bugs slip through.
Assertion Roulette
A test with many unlabeled assertions, so when one fails it is unclear which condition broke or why, slowing diagnosis.
Mystery Guest
A test that depends on external data or resources not visible in the test itself, making it opaque, fragile, and non-reproducible.
Happy-Path-Only Testing
Tests that exercise only the expected, valid flow and ignore errors, edge cases, and failures — leaving real-world conditions untested.
Excessive Mocking (Mockery)
Replacing nearly every collaborator with mocks so tests verify interactions instead of behavior, becoming brittle and detached from reality.
Slow Test Suite
A test suite so slow that developers stop running it locally and feedback arrives too late, encouraging skipped tests and large risky batches.
Coverage-Driven Testing (Coverage as a Target)
Chasing a code-coverage percentage as the goal, producing tests that execute code without meaningfully asserting behavior — high numbers, low confidence.
Checklists4
Post-Migration Validation Checklist
Validation checklist to confirm successful migration completion
Data Quality Validation Checklist
Checks for validating accuracy, completeness, consistency, and timeliness of data after a migration or pipeline change.
Core Web Vitals Performance Review Checklist
Review a web application against Core Web Vitals to improve loading, interactivity, and visual stability for real users.
Frontend Internationalization Readiness Checklist
Verify a web application is ready to support multiple languages, locales, and right-to-left layouts before internationalizing.
Benchmarks4
Code Coverage Benchmark
Measures the proportion of code exercised by automated tests, across line, branch, statement, and function coverage, as a test-completeness indicator.
Mutation Testing Score Benchmark
Measures test-suite effectiveness by injecting small faults into code and checking how many are detected, reported as the mutation score.
Flaky Test Rate Benchmark
Measures the prevalence and impact of nondeterministic tests that pass and fail without code changes, eroding trust in the test suite.
Defect Escape Rate Benchmark
Measures the proportion of defects that reach production undetected by pre-release testing, indicating the effectiveness of quality gates.
Glossaries3
Code Quality
A measure of how well-written, maintainable, and reliable source code is based on factors like readability, complexity, and test coverage
Performance
The measure of how efficiently a system executes tasks, typically evaluated through metrics like response time, throughput, and resource usage
Testing
The process of evaluating software to identify defects, verify functionality, and ensure quality