Architecturing Test Framework

on Microservice Project

L/O/G/O
 Contents

Architecturing not only on Test Framework but also its infrastructure

1 Monolithic vs Microservices

2 API Testing Fw and Implementation

3 Pipelining and Release Process

4 Code Implementation
Hot Tip

❖How to understand API Testing:

focus on contract communication that
defined.

▪On big feature, microservices growth fast, how

to fit the SDE culture : frequent commit and
once release
Monolithic vs Microservice
Monolithic vs Microservice (2)
Bizzy Solution Architect
Test Pyramid
Ancient test pyramid approach, still relevant

Made by SDET,
Functional Test End to End,
ex: Selenium, Appium
E2E

Made by SDET
API Test Integration

Made by SDE,
focus on smallest pieces
of code Unit Test

Text

Text
API Test Framework & Impl
 API Test Framework & Impl
(2)

Scalable Maintainable
Able to adopt if test is If changes happen, its
growing , and stable on easy to adapt and
current infra and implement. POP is a
architecture good approach

Ideal
Framework
Transparent Easy to Integrate
Framework should be Easy to integrate in
transparent to all related CI/CD process and
part. Ex: report result pipelining
and how the test work
Project Structure
 Pipelining & Release Process

Rule the branch commit, and

stream process from code to
Release. Git
Flow

Release Versioning and deploying

code on Staging area.
Process
Contd Contd
Intgr Delivery
Always perform test
On every commit and
merged on spc branch
Git Flow part of Release Pro
Release Process Overall
Feature Branch – Release Pro
Unit Test & Static Analysis-RP
Develop Branch – Release Pro
CRUD – API

https://developer.mozilla.org/en-US/docs/Web/HTTP/Status
Sedia Paramex oplos Bodrex
Newbie
Beginner
Intermediate
 Thank You!
Great workplace is stunning colleagues

L/O/G/O