QA Automation/Coding Revisited MindMap:
It is not about learn every piece of JAVA language first. please spend less time on syntax, use more time on coding to complete some your daily task.
-
Utilities Layers: Different Toolkits
- Configuration
- File/IO Handler
- OS Handlers
- Database Accessor
- CSV/EXCEL/XML/JSON/YAML Handler
- Different Clients:
- HTTP Client
- Redis Client
- Database Client
- Meta
- Reflection
- Class/Method/Arguments Resolver
- DI Container
-
Service Layer:
- DATA Access/Repository Layer
- Service Domain: Compose Different Repositories and API Integration
-
Integration/SDK Layer:
- Different SDKs to connect different Service
- Easy to Compose different integration and services
-
API Layer:
- Easy to Create Different Protocol API to exposure
- Easy to do API Registration
- fluent-builtin based-on different tools
Use java for QA Daily Work:
- code to handle different data and client:
- json/map
- csv/excel
- redis/http/database
- build internal admin system
- integration testing
- automation testing
- code to handle different data and client:
- fluentqa-data data access layers
- [] Excel/CSV Toolkit
- [] Mindmap Toolkit
- [] openapi toolkit
- [] Database Operation Simplify
- [] feishu/飞书
- [] vika 表格
- [] seatable
- [] .......
- modularization: compose different modules to build an app
- [] Generic DTO
- [] Generic Exceptions
- [] Logging Aspect
- [] spring starters
- [] Application Code Structures:
- Configuration
- API: 对外
- Service: 对内部,细颗粒度
- Repository: 数据访问层
- Configuration: 系统配置
- Core/Base: 常用方法和客户端组件调用方法/流程组合/控制反转/依赖注入
- [] Code Generate
- [] Database Table -> Entity/Repository/Service Code/Api Codes
- [] Different Templates Support/Configurable
- [] UI Code Generation