"Test Craftmanship: Crafting Continuously Evolving Test Strategy for Testing Micro Services" by Mayur Chitnis, Software Testing Specialist, Amdocs at #ATAGTR2021. #ATAGTR2021 was the 6th Edition of Global Testing Retreat. The video recording of the session is now available on the following link: https://www.youtube.com/watch?v=Ud54lj9jO70 To know more about #ATAGTR2021, please visit:https://www.youtube.com/watch?v=CzOLNti4V70

1. CRAFTING
CONTINUOUSLY
EVOLVING TEST
STRATEGY FOR
TESTING MICRO
SERVICES
AUTHOR : MAYUR CHITNIS
AUTHOR CODE – 045
AMDOCS , PUNE
DESIGNATION : SW TEST
SPECIALIST

2. SUMMARY
Title: Crafting Continuously Evolving Test Strategy for Testing Micro Services
Micro Service architecture offers you the advantages of breaking your business logic into multiple
services. With micro services architecture, business can aim faster product development with the help of
multiple parallel dev teams. On the other hand, shifting to ever evolving micro service architecture means
you need to adopt new development and test strategies. You test strategy plays very important role in
quality as well as the time to market of software.
What is importance of test craftmanship for testing Micro Services?
Test Craftmanship for QA, testing Micro Services is like being caddy for golfer.
In Micro Service world, QA’s main job comprises, is to prevent defects instead find them in higher
environment than dev environments. Test case design plays vital role in this case. After test case design,
which test case will come in which test layer (Unit, Micro Service, Contract etc.) comes as part of your
test strategy. Foundation of your test strategy is our mocking strategy. Mocks are of type: stubs, mocks,
virtual services. Which will be used where is another important aspect.
Test Design, Test strategy, Mocking Strategy are all inter linked. They are together in the journey of
product development. And their driver for this journey is test craftmanship.
Smart Test Case Design
Intelligent and Smart test case design of Micro Services testing involves very detailed and discipline
effort. While designing test case, we need to decide the type of test it will be.
Test strategy
After test case design, test strategy comes into picture. Quality of our testing lie on the strategy that we
have adopted.
Mocking Strategy
Mocking Strategy decides time to market of software. Efficient mocking strategy avoids duplicate effort in
testing same test case again and again. Selecting type of Mock, preparing test data for it, using it for test
(such as unit / component / integration etc) and who will be responsible for it, are all very important
aspects.
Test case design, test strategy and mocking strategy exhibit the quality of software product. And defines
how software development can be maintained in future.
Every software has something unique in its testing style. Also, every QA has his/her own unique way of
testing. Ultimately, testing is an art. To attain the certain level of test craftmanship, an individual should
work for considerable time on given product test development. Also, his/her contribution should be
towards improving quality and time to market of software.
Test solution architect can help his/her team gaining test craftmanship at individual level. Test solution
architects are those who are not just technology focused but they are responsible for building QA
processes. Test solution architect is our CAPATAIN of the test craftman-SHIP.
Test Craftmanship in testing Micro Services is ever evolving process and it should be evaluated time to
time.

3. Agility is about building the right thing,
Craftsmanship is about building the
thing right
CRAFT ,
CRAFTMANSHIP
AND TEST
CRAFTMANSHIP
craft
an activity involving skill in making
things by hand
Craftsmanship
skill in a particular craft
Test Craftmanship
Building process to test Software
with highly skilled professionals ..

4. “The golden rule: can you make a change to a
service and deploy it by itself without
changing anything else?”

7. “IF YOU ARE SELFISH… THEN YOU
SHOULD MAKE PERSON-LESS API .”

8. TEST CRAFTMANSHIP FOR
‘TESTWARE’
In any software project , most important deliverable is Software;
But,
Tests are the single most effective way of documenting business
requirements
And,
In the world of Micro Services , everyone is fan of ‘Shift-Left’ Practice
Where ,
Test Automation is back-bone of any ‘Shift-Left’ Practice
Also,
No one writes tests to test automated tests written
So,
For Continuous Integrated and Continuous Delivery , Test Craftmanship
plays vital role , to build ‘Testware’ which is robust , fast and has well
covered functional tests.

9. CRAFTING YOUR CODE ? “FOCUS ON WHAT
ARE YOU DOING INSTEAD WHY YOU DOING
IT”
Domain Specific
Language – Easy to
read
Less Complex –
Easy to maintain
No hard coded test
data – makes test
repeatable , crisp
and clear
Relevant assertions
– Write should &
expect methods,
conditional and
guard asserts
Less Test code –
Less test failures.
Write test names
as a process.

10. DON’T WRITE TEST FOR COMPILER ..
Test without DSL
import applicationDriver
import applicationClicker
import AssertapplicationDriver.create()
theWindow =
applicationDriver.getWindow("Welcome
Screen")
buttonResult =
applicationClicker.leftClickOnButton(theWin
dow, "theButtonName")
applicationDriver.close()Assert(buttonResult
).isNotEmpty()
Test with DSL
import dsl
import theWindow
import AsserttheWindow {
perform leftClick on theButton
clickResult = getResult()
Assert(clickResult).isNotEmpty()

11. NO CONDITIONAL ASSERTS PLS ..
Avoid conditional Asserts ..
@Test public void test()
{
if (systemIsInStateA()) {
assertThat(system,
shouldPerformInWay(X));
} else {
assertThat(system,
shouldPerformInWay(Y));
} }
Use Test Specific Assert
Statements
@Test public void testStateA()
{
assertThat(system, shouldPerformInWay(X));
}
@Test public void testStateB()
{
assertThat(system, shouldPerformInWay(Y));
}

12. DON’T HARD CODE YOUR TEST DATA ..
Hard coded test data ..
public function
testGetTranslationFileTimestamp()
{
$this->fileManagerMock->expects($this-
>once())
->method('getTranslationFileTimestamp')
->willReturn(1445736974);
$this->assertEquals(1445736974, $this-
>model->getTranslationFileTimestamp());
}
Instead Parameterized it ..
public function testGetTranslationFileTimestamp()
{
$translationFileTimestamp = 1445736974;
$this->fileManagerMock->expects($this->once())
->method('getTranslationFileTimestamp')
->willReturn($translationFileTimestamp);
$this->assertEquals($translationFileTimestamp,
$this->model->getTranslationFileTimestamp());
}

13. TEST TOOL ..
“FAST, GOOD,
CHEAP: PICK ANY
TWO.”
At one side you have your test
strategy and at other side you list of
tools to choose one test tool from it.
Tool selection should be from the
perspective of Functional and Non-
functional both.
Tool preference also depends on type
of test

14. “IN
TIME OF
TEST ,
FAMILY IS
BEST …”
• Tool preference also depends on type of test.
• Such as ..
• Component test aka. Service level test will look for tool
• Where test can be written in tear down approach
• Which has easy integration with external components such
as DB , Kafka
• Where external dependencies can be mocked , stubs can
be integrated easily
• Where QA can write human readable script from business
user point of view
• Contract test aka. Integration test will look for tool
• Where test can be written from consumer and producer
point of view.
• Where tests can be easily shared between consumer
and producer service.
• Where service virtualization is available in built

15. 0
4
2
0.3
0
0
0.5
2
4
0
PLAN & DESIGN DEVELOP & BUILD TEST DEPLOY & RELEASE MONITOR & ANALYZE
Attention
To
Quality
Built in Quality
Shift Left Traditional
ULTIMATE GOAL : SHIFT LEFT

16. I AM SOFTWARE TEST
DEVELOPER
Hi, I am Martin. I am SW Test Developer.
My job is to prevent bug before build gets
deployed in higher environments.
I do write maintainable test ware, so that my
fellow test developers can happily make
additions to test.

17. EVOLUTION OF SW
TEST DEVELOPER

19. GOAL OF SW
TEST
DEVELOPER
Knowledge : Understand tools and
techniques , use them wisely.
Skill : Ability to apply one’s scientific and
artistic knowledge
Diligence : Put your constant efforts and
time to achieve quality output. Craftsman
possess ability to balance between need
for quality and need for speed.
Judgement : Craftsman combines
experience , common sense and
institution to create valuable product.

20. REFERENCES
• The Software Craftsman By Sandro Mancuso
• Testing Java Microservices: Using Arquillian,
Hoverfly, AssertJ, JUnit, Selenium, and Mockito
• The Art of Unit Testing, 2nd Edition
• https://testcraftsmanship.com/#about

21. ABOUT AUTHOR
• Hard core software QA at heart. Over 15 plus
years of experience in the software industry.
Initially started my career as software
developer, later moved to software testing.
Currently working as a Software Test Specialist
at Amdocs development center, Pune. For the
last 8 years , I have been working as an API
test engineer for developing products in the
Payment industry.
• Enjoy being an innovation enthusiast. Won
several innovation contests at
organizational level. Always ready to bring new
ideas and innovation in day to day work.
• I am responsible for driving all QA activities
and implementing QA best practices at my
project level. Have delivered sessions on Micro
services testing at my organization level.
• I strongly believe that learning is a
continuous process. Always ready to learn new
things and contribute from my side in the area
of Micro services , cloud computing, devops,

22. THANK YOU
!!