[resultui] replace build page unit tests with integration tests

Build page unit tests are fragile due to increasingly complex mocking
requirements. Integration tests require less mocking therefore are less
likely to break.

R=bryner, gavinmak@google.com

Change-Id: Iac90d2c39fab4d65fd87a993901f693f1b37f997
Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/luci-go/+/2951844
Reviewed-by: Gavin Mak <gavinmak@google.com>
Commit-Queue: Weiwei Lin <weiweilin@google.com>
Auto-Submit: Weiwei Lin <weiweilin@google.com>
6 files changed
tree: 20ebf5e15c670581e252861ece627b9c56f7f264
  1. .gitallowed
  2. .gitattributes
  3. .gitignore
  4. .golangci.yml
  5. AUTHORS
  6. CONTRIBUTING.md
  7. CONTRIBUTORS
  8. LICENSE
  9. OWNERS
  10. PRESUBMIT.py
  11. README.md
  12. WATCHLISTS
  13. appengine/
  14. auth/
  15. buildbucket/
  16. casviewer/
  17. cipd/
  18. client/
  19. cmdrunner/
  20. codereview.settings
  21. common/
  22. config/
  23. cq/
  24. cv/
  25. dm/
  26. examples/
  27. gae/
  28. gce/
  29. grpc/
  30. hacks/
  31. hardcoded/
  32. led/
  33. logdog/
  34. luci_notify/
  35. lucicfg/
  36. lucictx/
  37. luciexe/
  38. machine-db/
  39. milo/
  40. mmutex/
  41. mp/
  42. resultdb/
  43. scheduler/
  44. server/
  45. starlark/
  46. swarming/
  47. tokenserver/
  48. tools/
  49. tumble/
  50. vpython/
  51. web/
README.md

luci-go: LUCI services and tools in Go

GoDoc

Installing

LUCI Go code is meant to be worked on from an Chromium infra.git checkout, which enforces packages versions and Go toolchain version. First get fetch via depot_tools.git then run:

fetch infra
cd infra/go
eval `./env.py`
cd src/go.chromium.org/luci

Contributing

Contributing uses the same flow as Chromium contributions.