Dataplatforms evolve by solving 'first' ,the 'one' business problem that an existing system cannot solve or solves in a very painful way and uses this 'first' success to drive adoption. While a huge amount of effort is required in building a platform from the ground up , it is very easy to be distracted (rightfully) by the 'one' usecase/application that will decide the future of the platform. How do we ensure the speed of development of the application and the quality of the platform on which the application lives , at the same time ? The order in which things are built ( platform components/features vs application features ) dictate how testing evolves for the whole lot. This talk is to share how ours evolved..

1. QAing a Data Platform
Kalyan Muthiah

2. Data Platform
Write to / Read from
Publish &
Subscribe
React to Events
Reliable Event
Source
Real time stream processing
systems
Keep a Log of events

3. Publish & Subscribe

4. React to data

5. Reliable Event Store

6. ROLE OF A QA
VERIFY
VALIDAT
E
DEV
BADEVOPS QA

7. Evolution of Platform

8. Platform Vs Apps

9. Platforms have behaviours
Availability over Integrity ?
Source of truth over Accuracy of data ?

10. Role of a QA

11. High Level Components
DATA SOURCE CONNECTOR
KAFKA
DATA SINK
KAFKA STREAM
APPLICATION
ZOO KEEPER
SCHEM A REGISTRY

12. Test Pyramid - Planned Vs Actual
E2E
Integration
Component
Unit
E2E
Integration
Component
Unit
Integration
Component
Unit
Unit tests that ran against
Embedded Kafka
Integration

13. Monitoring complimented Tests
E2E
Integration
Component
Unit
E2E
Unit
Unit

14. Nothing like End-To-End Tests

15. Evolution of usage of E2E tests
E2E
Integration
Component
Unit
KAFKA
ZOOKEEPER
TOOLS
STREAMING
APP
E2E
BUILD ENTIRE CLUSTER TEST

16. Evolution of usage of E2E tests
E2E
Integration
Component
Unit
KAFKA
ZOOKEEPER TOOLS
STREAMING
APP
E2E E2E E2E E2E
BUILD ONE COMPONENT
TEST

17. How the E2E test feedback
● Understand the degree of stability of the cluster & apps
● Served as a means to eliminate problems in cluster (Debug)

18. Introduce one component at a
time

19. Cluster - Weight Loss Programme

20. Bulk Volume E2E Tests
● Importance of Schema management
● Replay situations
● Data Integrity ( Duplicates )
● CPU utilisation

21. THANK YOU
For questions or suggestions:
Your Name
you@ThoughtWorks.com