No Code

 Service testing   Build(CI)->deploy to Dev(CD)->Unit test API methods HTTP properties Service security Request validation UI Test  Build(CI)->deploy to Dev(CD)->Unit test Consistency of visual elements Spelling Typography Behaviour of interactive elements Interactive elements Functional validation of actions Adaptability with different devices  Integration/functional and UAT test Unit test(including UI and Service )->Deploy service (integrated environment)-> deploy UI, deploy service>Integrated testing->UAT Functional test User journey test NFR Test Pre-prod/Load test The response time Throughput Environment Process time Interoperability Base load  Breaking load   https://www.testim.io/blog/ui-testing-beginners-guide/ https://www.softwaretestinghelp.com/what-is-non-functional-testing/#Non-Functional_Test_Cases_Checklist

 CI: A ll newly  c hecked-in code properly integrates with existing code branch out->checkout->code->verify code(compiles)->UT->checkin->PR->merge->branch merge->build->binary to repository Run it periodically-daily(recommended)/few time in week/weekly Test suite and run with every new build Repo options: Single monolithic repo->single build all code(all MS)->multiple binary: single team responsible for all code Single monolithic repo->Multiple build one per MS->multiple binary one per MS: multiple team responsible for their code Multiple repo one per MS->one build per MS->one binary per MS: multiple team responsible for their code CI options Automated and triggers with each code checkin Manual, periodic based on teams agreement CD Single platform and OS scenario:  Multi platform and OS scenario: Automate Approach Base VM->deploy platform->add custom configuration for service->deploy service artefact Crea...

 Service to host mapping Self managed Multiple services per host ease of host management lower cost will off set with managing  virtualisation Difficult to monitor shared resources(CPU) Larger impact on host failure, impact analysis will be difficult Difficult to manage dependency on each service Containerisation: One service per container: multiple containers per host  One service per host  Platform as a service Serverless Host virtualisation options VM based virtualisation layers Machine Kernel Host OS Hypervisor VM Kernel VM OS Apps Container based virtualisation layers Machine Kernel Host OS Container engine Bins/libs Apps