Please enable JavaScript.
Coggle requires JavaScript to display documents.
Hardening - Coggle Diagram
Hardening
Outcomes
More Experienced QA
New QA build experience of products
QA Understand Expectations
Set precedent for future hardening
Identify QA Leaders/Community
to Drive Continuous Improvements
More Experienced Developers
New Developers build experience of products
Developers Understand Expectations
Better Understanding of Existing
Automation Test Coverage
(
Teams justify manual test cases
)
Set Confidence Level
Direct Hardening Activities
Identify Gaps
Execute Plan
to Plug Gaps
Higher Confidence Level
Shorter Hardening Sprints in Future
Higher Overall Quality
Identify Test Cases which Can Be Automated which Have Not Been
Create End-to-end Integration Tests
All QA Understand
What is Available
Build Better Exploritory
Test Plans in Future
Inventory of Test Automation (Serenity)
Build Confluence Page which References all Feature Reports
Identify Test Cases which cannot be automated
Quality Release
No Installation Issues
(Yes)
Perform Thorough set of
Installation Tests
Upgrades
4.14
Windows Server 2016
4.15
Windows Server 2016
Customer DBs
RBS / HSBC Mexico
4.16
Windows Server 2019
Fresh Installs
Windows Server 2019
Setup a Domain Controller
to better reflect customer environments.
SQL Server Windows Authentication
Automate All Fresh /
Upgrade Test Combinations
No P1/P2 Functional Defects
Non Functional Tests
Penetration Test
Performance Testing
DR Testing
Resiliency Testing
(
Yes
)
SQL Server
Failover Testing
ZooKeeper Failover
ActiveMQ Failover
Apache Solr
Investment Per-release
Sajid's Test Cases
(
Yes
)
Hardening Bugs
RCA must be completed
(Must know the RC as the code is new).
Dev and QA SMEs must review later changes:
Himanshi / Prabhjot / Siri / Steph
Dev and QA SMEs to identify regression test cases
Automated Code Scanning /
Clean Up
Whitesource Vulnerability Dependencies
Coverity Secure Coding Practices
SonarQube
Ensure we are generating all charts;
Code coverage not generating
All changes depend on automated unit / integration code coverage to ensure no fix-on-fix bugs are introduced
Logs are noisy and unusable for monitoring. Need to be cleaned up.
Makes it time consuming/inefficient
Address the Internal Backlog (P3)
Stop releasing with more and more internal bugs
Documentation
Maintain the Quality / Dont go backwards
Audit Adherence to Process
100% unit test coverage
for all changes (Production + R&D)
Automated Integration Tests
Zero Sonar Violations
All CI Green
Implement Corrective Actions / Training
Culture
What is our culture ?
Information Management Challenges
Root Cause Analysis
90% IG vs 10% NCR
Latest RCA
Scrum-of-Scrums
Review Unmapped Test Cases
Review Roadblocks
Review Raised Defects + Assignments
Review Test Case Burndown
Review JIRAs Found Outwith Planned Activities
Leads
(ATL + DND) Pankaj Ingle
(HYD)
Vidya Sagar /
Srinivasa rao Itamsetti
(IG)
Priyanka Rawat
Nidhi Gupta
Pushpank