От хаоса к автоматизации тестирования на примере backend

61
1 CONFIDENTIAL Testing of the backend system October 15, 2016 FROM CHAOS TO TEST AUTOMATION

Upload: comaqaby

Post on 09-Jan-2017

140 views

Category:

Technology


1 download

TRANSCRIPT

Page 1: От хаоса к автоматизации тестирования на примере Backend

1CONFIDENTIAL

Testing of the backend systemOctober 15, 2016

FROM CHAOS TO TEST AUTOMATION

Page 2: От хаоса к автоматизации тестирования на примере Backend

2CONFIDENTIAL

ROMAN SOROKA• Lead test automation engineer in EPAM

• Activist of COMAQA.by community• Over 7 years in IT.

• Relocated to Minsk from Moscow

• Roles in the career: developer, software engineer in test, QA lead, delivery manager.

Page 3: От хаоса к автоматизации тестирования на примере Backend

3CONFIDENTIAL

I am from Sarov

Page 4: От хаоса к автоматизации тестирования на примере Backend

4CONFIDENTIAL

Why Minsk

Minsk =

= Moscow

Page 5: От хаоса к автоматизации тестирования на примере Backend

5CONFIDENTIAL

Why Minsk

Minsk =

= Moscow

Page 6: От хаоса к автоматизации тестирования на примере Backend

6CONFIDENTIAL

Why Minsk

Minsk =

= Moscow

Page 7: От хаоса к автоматизации тестирования на примере Backend

7CONFIDENTIAL

Why Minsk

Minsk =

= Moscow

Page 8: От хаоса к автоматизации тестирования на примере Backend

8CONFIDENTIAL

Why Minsk

Minsk =

Page 9: От хаоса к автоматизации тестирования на примере Backend

9CONFIDENTIAL

Why Minsk

MinskEPAM =

>4000epamers

Page 11: От хаоса к автоматизации тестирования на примере Backend

11CONFIDENTIAL

The ground rules

25 minutes 15

minutes

Page 12: От хаоса к автоматизации тестирования на примере Backend

12CONFIDENTIAL

1 2 3 4

Agenda

The first steps on the project

Dealing with chaos Selling the test automation

The framework architecture inside

out

Page 13: От хаоса к автоматизации тестирования на примере Backend

13CONFIDENTIAL

Intro

Page 14: От хаоса к автоматизации тестирования на примере Backend

14CONFIDENTIAL

Intro

Page 15: От хаоса к автоматизации тестирования на примере Backend

15CONFIDENTIAL

The first steps on the project

Page 16: От хаоса к автоматизации тестирования на примере Backend

16CONFIDENTIAL

Expectation vs Reality

Page 17: От хаоса к автоматизации тестирования на примере Backend

17CONFIDENTIAL

Expectation vs Reality

Page 18: От хаоса к автоматизации тестирования на примере Backend

18CONFIDENTIAL

EXPECTATION REALITY

Expectation vs Reality

Clear workflow

Specified acceptance criteriaUsable documentation

Good working autotests

Page 19: От хаоса к автоматизации тестирования на примере Backend

19CONFIDENTIAL

•Ask questions•Confirm answers or their absence•Fill the knowledge base

Solutions

Page 20: От хаоса к автоматизации тестирования на примере Backend

20CONFIDENTIAL

Knowledge transfer

Find out what was expected from your predecessor!Make sure that Customer knows how it was done!

Page 21: От хаоса к автоматизации тестирования на примере Backend

21CONFIDENTIAL

Ask questions

Page 22: От хаоса к автоматизации тестирования на примере Backend

22CONFIDENTIAL

Get confirmation

Page 23: От хаоса к автоматизации тестирования на примере Backend

23CONFIDENTIAL

Ask questions again

Page 24: От хаоса к автоматизации тестирования на примере Backend

24CONFIDENTIAL

Summary for the first steps

•Gather knowledge as many as possible!

•There are no too many stupid question to ask!

Page 25: От хаоса к автоматизации тестирования на примере Backend

25CONFIDENTIAL

Kb.e

pam

.co mThink

about yourself in the future and other people!

Fill the knowledge base

Page 26: От хаоса к автоматизации тестирования на примере Backend

26CONFIDENTIAL

Dealing with chaos

Page 27: От хаоса к автоматизации тестирования на примере Backend

27CONFIDENTIAL

•Earn trust and respect•Make friends•Find out the politics behind•Start offering incremental improvements

Solutions

Page 28: От хаоса к автоматизации тестирования на примере Backend

28CONFIDENTIAL

Earn respect

Do some simple and required task much better then it was done before!Use it as an example of good work!

Page 29: От хаоса к автоматизации тестирования на примере Backend

29CONFIDENTIAL

Earn respect

Get known for your knowledge and understanding of the job

Page 30: От хаоса к автоматизации тестирования на примере Backend

30CONFIDENTIAL

Earn trust

Help out people if you can!It will earn their trust.

Page 31: От хаоса к автоматизации тестирования на примере Backend

31CONFIDENTIAL

Make friends

Invest in good relationships! They help in achieving all goals!

Page 32: От хаоса к автоматизации тестирования на примере Backend

32CONFIDENTIAL

Politics behind

Page 33: От хаоса к автоматизации тестирования на примере Backend

33CONFIDENTIAL

Find allies

Page 34: От хаоса к автоматизации тестирования на примере Backend

34CONFIDENTIAL

Find allies

Find ones who can be trusted.

Page 35: От хаоса к автоматизации тестирования на примере Backend

35CONFIDENTIAL

Find out why the things are in the current state of affairs!

Find out reasons

Page 36: От хаоса к автоматизации тестирования на примере Backend

36CONFIDENTIAL

Find out reasons

We need to show the Client that we can achieve the expected results!

Page 37: От хаоса к автоматизации тестирования на примере Backend

37CONFIDENTIAL

Incremental improvements

Propose to improve some small thing which will give the meaningful value!

Page 38: От хаоса к автоматизации тестирования на примере Backend

38CONFIDENTIAL

Incremental improvements

Page 39: От хаоса к автоматизации тестирования на примере Backend

39CONFIDENTIAL

Incremental improvements

Page 40: От хаоса к автоматизации тестирования на примере Backend

40CONFIDENTIAL

Selling test automation

Page 41: От хаоса к автоматизации тестирования на примере Backend

41CONFIDENTIAL

•Ask advices•Gather facts•Calculate benefits•Present the proposition to the customer

Solutions

Page 42: От хаоса к автоматизации тестирования на примере Backend

42CONFIDENTIAL

Ask advices

Page 43: От хаоса к автоматизации тестирования на примере Backend

43CONFIDENTIAL

• The number of defects detected in production in Jan-Jul 2016 is twice higher than in the same period 2015.

• The ratio of defects detected in production amounts to 31.5%. (The industry recommended value is less than 10%)

• The total sanity test coverage amounts to 34%. (The value recommended by customer standards is above 80%.)

• The immediate test automation technical debt is more than 1000h.

• The development team spends up to 30% on the bug fixing per iteration.

Gather facts

Page 44: От хаоса к автоматизации тестирования на примере Backend

44CONFIDENTIAL

Calculate benefits

  Time to implement the suggested TAF

  Elimination of the technical debt

  Time savings with the new TAF 

1 key tester works 64 hours per iteration in the ideal time in both cases for the elimination of the debt only

Existing TAF                       25

i1 i3 i5 i7 i9 i11 i13 i15 i17 i19 i21 i23           

Suggested TAF    5        7        

  13

i1 i3 i5 i7 i9 i11  i12  i13 i15 i17 i19 i21 i23

Page 45: От хаоса к автоматизации тестирования на примере Backend

45CONFIDENTIAL

Present proposition to the customer

Page 46: От хаоса к автоматизации тестирования на примере Backend

46CONFIDENTIAL

Be flexible

Page 47: От хаоса к автоматизации тестирования на примере Backend

47CONFIDENTIAL

The framework architecture inside out

Page 48: От хаоса к автоматизации тестирования на примере Backend

48CONFIDENTIAL

BACK-END. What’s that?

Page 49: От хаоса к автоматизации тестирования на примере Backend

49CONFIDENTIAL

•Allow the computer to do the math for you•Collaborate with developers•Use the cases as the documentation•Make it easy for other people to use•Create easy readable results of testing

Solutions

Page 50: От хаоса к автоматизации тестирования на примере Backend

50CONFIDENTIAL

Allow the computer to do the math for you

Create a sanity test caseCreate all positive requests with

required fields

Create all negative requests without required fields

Create all positive requests within boundary conditions

Create all negative requests outside boundary conditions

Create all positive requests with correct type of arguments

Page 51: От хаоса к автоматизации тестирования на примере Backend

51CONFIDENTIAL

Use TAF to generate all available permutations of test cases.People don’t need to think about each available combination it should be done automatically once the requirements are specified.

1

Soltuion#1

Page 52: От хаоса к автоматизации тестирования на примере Backend

52CONFIDENTIAL

Collaborate with developers

Page 53: От хаоса к автоматизации тестирования на примере Backend

53CONFIDENTIAL

Take the functional created by developers don’t reinvent the wheel. Use development code data base as well.

2

Soltuion#2

Page 54: От хаоса к автоматизации тестирования на примере Backend

54CONFIDENTIAL

Use the cases as the documentation

Page 55: От хаоса к автоматизации тестирования на примере Backend

55CONFIDENTIAL

Use TAF to generate the most actual and comprehensive documentation from your test cases.It will contain working request and real responses and be always up to date and be complied with the acceptance criteria for the task.

3

Soltuion#2

Page 56: От хаоса к автоматизации тестирования на примере Backend

56CONFIDENTIAL

Make it easy for other people to use

Once the framework is created anyone without automation knowledge should be able to add test cases to it!

Page 57: От хаоса к автоматизации тестирования на примере Backend

57CONFIDENTIAL

Create TAF to allow adding cases even to business people if they want it.Adding test cases should not require knowledge beyond the average computer user.

4

Soltuion#3

Page 58: От хаоса к автоматизации тестирования на примере Backend

58CONFIDENTIAL

Create easy readable results of testingCreate easy readable results of testing

Page 59: От хаоса к автоматизации тестирования на примере Backend

59CONFIDENTIAL

Write in the main log only really useful information on the state of affairs.Logs and results should not contain all the information, but the necessary one which allows to quickly identify the root cause of the problem.

5

Soltuion#4

Page 60: От хаоса к автоматизации тестирования на примере Backend

60CONFIDENTIAL

THANK YOU FOR ATTENTION!

??? QUESTIONS ??

?

Page 61: От хаоса к автоматизации тестирования на примере Backend

61CONFIDENTIAL

Create easy readable results of testingTHE END