Don't you like Integration testing as Me&

Slides of public talk at SeleniumCamp 2018

Transcript

1. Don’t you like Integration testing as Me?
2. Yevhen Rudiev • QA Automation Lead at GamePoint • ~6 years experience in IT • ~3 years experience in Automated Testing • ~2 years experience in Micro- Service architecture
3. INTEGRATION TESTING
4. INTEGRATION TESTING
5. INTEGRATION TESTING
6. INTEGRATION TESTING
9. HOW TO TEST IT?
10. #1 END TO END TESTING
11. System under test DB Test Provider
12. #1.1 PROBLEMS: • Test data
13. TEST DATA <PayPointSettings> <MerchantId>1234</MerchantId> <MerchantPassword>Password</MerchantPassword> <Url>https://TestPayPoint.com/Payment</Url> <ApiVersion>v2.1</ApiVersion> <SecretWord>SecretWord</SecretWord> </PayPointSettings>
14. TEST DATA [Test] public void VisaDeposit_Positive_PaymentCaptured() { BuildPaymentRequest(PaymentType.Deposit) .WithProvider(TestData.PayPointProviderName) .WithPaymentMethod(TestData.Visa) .WithCreditCardNumber(TestData.PositiveCardPayPoint) .WithExpectedFinalStatus(PaymentStatus.Captured) .Send(); }
15. TEST DATA [Test] public void VisaDeposit_Positive_PaymentCaptured() { BuildPaymentRequest(PaymentType.Deposit) .WithProvider(TestData.PayPointProviderName) .WithPaymentMethod(TestData.Visa) .WithCreditCardNumber(TestData.PositiveCardPayPoint) .WithExpectedFinalStatus(PaymentStatus.Captured) .Send(); }
16. TEST DATA [Test] public void VisaDeposit_Negative_PaymentRefused() { BuildPaymentRequest(PaymentType.Deposit) .WithProvider(TestData.PayPointProviderName) .WithPaymentMethod(TestData.Visa) .WithCreditCardNumber(TestData.RefusedCardPayPoint) .WithExpectedFinalStatus(PaymentStatus.Refused) .Send(); }
17. TEST DATA <SkrillSettings> <Login>Name</Login> <ApiPassword>Password</ApiPassword> <PublicKey>PublicPassword</PublicKey> <PrivateKey>PrivatePassword</PrivateKey> <Url>https://TestPayPoint.com/Payment</Url> </SkrillSettings >
18. TEST DATA [Test] public void SkrilWithdrawal_PaymentRefused() { BuildPaymentRequest(PaymentType.Withdrawal) .WithAmount(TestData.NegativeAmountSkrill) .WithExpectedFinalStatus(PaymentStatus.Refused) .Send(); }
19. #1.1 PROBLEMS: • Test data • Fail investigation
20. FAIL INVESTIGATION Test Failed: PaymentStatus was not updated to Captured in 30 seconds Expected: Captured Actual: Refused
21. Provider System under test FAIL INVESTIGATION Test Provider Test System under test System under test
22. #1.1 PROBLEMS: • Test data • Fail investigation • Speed
23. System under test SPEED DB Test Provider
25. SPEED DB Provider Additional services
26. #1.1 PROBLEMS: • Test data • Fail investigation • Speed • Stability
27. • New unstable version • WebRequest.Timeout • Delayed responses • Test Data changes • Hardware issues STABILITY
28. #2 TESTING WITH FAKES
29. #2.1 PRINCIPLE Fake of Provider Provider DB
30. System under test #2.1 PRINCIPLE DB Test Fake of Provider Provider
31. #2.1 PRINCIPLE HOST Provider 1 Provider 2 Provider N System under test
32. #2.2 E2E TESTING PROBLEMS: • Test data • Fail investigation • Speed • Stability
33. TEST DATA HOST Behavior Context Provider N Test
34. BEHAVIOR CONTEXT GET Request http://Testing.Fakes/BehaviorContext? paymentId={0}&status={1} ConcurrentDictionary<string,string>
35. BEHAVIOR CONTEXT [Test] public void VisaDeposit_Positive_PaymentCaptured() { BuildPaymentRequest(PaymentType.Deposit) .WithProvider(TestData.PayPointProviderName) .WithPaymentMethod(TestData.Visa) .WithCreditCardNumber(TestData.PositiveCardPayPoint) .WithExpectedFinalStatus(PaymentStatus.Captured) .Send(); }
36. BEHAVIOR CONTEXT [Test] public void VisaDeposit_Positive_PaymentCaptured() { BuildPaymentRequest(PaymentType.Deposit) .WithProvider(TestData.PayPointProviderName) .WithPaymentMethod(TestData.Visa) .WithBehavior(req => BehaviorHelper.Set(req.PaymentId, PaymentStatus.Captured)) .WithExpectedFinalStatus(PaymentStatus.Captured) .Send(); }
37. #2.2 E2E TESTING PROBLEMS: • Test data • Fail investigation • Speed • Stability
38. System under test System under test Provider FAIL INVESTIGATION Test Test
39. • Test data • Fail investigation • Speed • Stability #2.2 E2E TESTING PROBLEMS:
40. SPEED HOST System under test Fake of Provider localhost
41. • Test data • Fail investigation • Speed • Stability #2.2 E2E TESTING PROBLEMS:
42. STABILITY • New unstable version • WebRequest.Timeout • Delayed responses • Test Data changes • Hardware issues
43. #2.2 E2E TESTING PROBLEMS: • Test data • Fail investigation • Speed • Stability
44. PRICE: • Higher tech level of QA • Increased time of development • More code to support • Synchronize Changes
45. Do we still need integration testing?
46. Fake of Provider System under test DB Test
47. REQUEST VALIDATION “b50cb600-ddd4-4cea-a4ce-0f266a33e922” => “John1990” “johndoe@gmail.com” => “John Doe” “en” => “English” “EUR” => “USD”
49. E2E TESTING PROBLEMS: • Test data • Fail investigation • Speed • Stability
51. #3 SMART FAKES
52. System under test #3 SMART FAKES DB Test Fake of Provider Verification of request
53. #3.1 ISupportLogging public void ProcessRequest(HttpContext context) { logger.Log(context.Request.PaymentId, context.Request); return BehaviorContext.Response(context.Request.PaymentId); }
54. #3.1 ISupportLogging [Test] public void VisaDeposit_Positive_PaymentCaptured() { . . . var request = FakeHelper.GetRequest(payment.Id); AssertRequest(request); } public void AssertRequest(HttpRequest request)
55. #3.2 ISupportValidation public void ProcessRequest(HttpContext context) { if (!IsValidRequest(context.Request)) { return BadRequest(“Request violates the contract”); } return BehaviorContext.Response(context.Request.PaymentId); }
56. #3.2 ISupportValidation [Test] public void VisaDeposit_Positive_PaymentCaptured() { BuildPaymentRequest(PaymentType.Deposit) .WithProvider(TestData.PayPointProviderName) .WithPaymentMethod(TestData.Visa) .WithBehavior(req => BehaviorHelper.Set(req.PaymentId, PaymentStatus.Captured)) .WithExpectedFinalStatus(PaymentStatus.Captured) .Send(); }
57. #3.3 PLUSSES: • All plusses from Fakes approach: • Fast • Stable • Controlled • Request verification
58. #3.4 BLIND SPOTS: • Changes in the contracts on prod • New integration testing • Documentation errors
59. #3.5 MICROSERVICES TESTING Microservice #1 Microservice #2 Microservice #3 Microservice #4 Microservice #5
60. Smart Fake #5 #3.5 MICROSERVICES TESTING Microservice #1 Smart Fake #2 Smart Fake #3 Smart Fake #4
61. RESULTS • Made our tests faster, more stable and controlled • Fakes guaranteed integration compatibility • Lives became easier
62. ALWAYS LOOK FOR THE IMPROVEMENTS
63. CONTACTS: www.linkedin.com/in/yevhen-rudiev-a5609590 www.facebook.com/evgeniy.rudev.5
64. Q&A