This document discusses using Go to implement functional verification testing. It begins by explaining go test and unit testing. It then defines functional verification testing as testing how users use an application across packages or microservices, as opposed to unit testing individual functions. It describes setting up test scenarios, running tests against API endpoints, and having a test server manage state and collect results. The document recommends designing test cases, implementing a test server to run cases and report reactions, and addresses issues like managing authentication and avoiding overloading the server.

1. Functional verification test framework with Go
Rain Wu

2. About Me
Communities
Python
Go
Technical Artist
Web Backend
Writer
Business
Economic
Negotiation

3. Agenda
- go test
- unit test v.s. functional verification test
- scenario & requirements
- design & implement

4. go test
“testing” package

5. How go test/testing package do?
- user-defined test cases
- manage the states
- show the results

6. Unit test cases

9. Run unit test

10. If an error occurs…

11. (t *testing.T)

12. The document

13. The source code (release-branch.go1.14)

16. Unit test

17. Unit test
- Individual functions or packages work correctly
- Developer's responsibility

18. Unit test
- But I also run it in CI because they often forget

20. Functional verification test

21. Functional verification test
- How users use, not how developers develop
- Cross packages, or even cross micro-services

23. Bottleneck
- Need to really start the service
- Even need infrastructure and environment

24. Scenario

25. Test web server’s API via requests
ServiceScripts

26. Some test cases
- Find a seat to sit down
- Come to the counter to order and pay
- Make a reservation

27. We hope to get the results of all tests at once
- Find a seat to sit down
- FAILED : no seats left
- Come to the counter to order and pay
- PASSED
- Make a reservation
- PASSED

28. Unless the test beats the service
- Find a seat to sit down
- FAILED : no seats left
- Come to the counter to order and pay
- Connection refused
- Make a reservation

29. Advanced information
- Find a seat to sit down
- Seating area 1F-A : 23/23
- Seating area 1F-B : 17/17
- Seating area 1F-C : 17/17
- Seating area 2F : 0/0
- FAILED : no seats left

30. Who can run the test
QC
Backend
Frontend
PM
SRE

31. Design & Implement

32. Service
Scripts
Server to run tests
Run test
Reaction
Order Report

33. Server to run tests
InfrastructureEnvironment
Host Test casesAPI endpoints

34. API endpoints
- POST /orders
- GET /orders?timestamp>1595721600&timestamp<1595808000
- GET /results?tester=rain
- GET /results/002020
- POST /testers
- GET /testers

35. Manage state & collect information

37. Warning

38. Server to run tests
Host test cases
Password
Token

39. Too busy

41. References
- Photos from Unsplash
- github.com/golang/go

42. Thanks for listening
ID: Rain Wu