Skip to content

Release Qualification

Filip Barl edited this page May 21, 2019 · 10 revisions

Things to test before a release, not currently covered by our integration tests:

  • Start a 2 node cluster and leave a UI connected, watch for performance regression
  • Run a Scope cluster on ECS
  • Run Scope on https://github.com/microservices-demo/microservices-demo/
  • Run Scope on Docker For Mac
  • Start and stop Scope in standalone mode
    • Linux
    • docker-machine
  • Connect probes from release candidate to Weave Cloud
    • Local scope in probe-only mode connects to Weave Cloud and renders correctly
      • dev
      • prod
    • Controls appear for containers and function correctly
      • dev
      • prod
    • No new errors in logging or telemetry
      • dev
      • prod
  • UI integration
    • Hot-reloading cd client && yarn install && yarn start and open http://localhost:4042
    • UI under prefix path cd client && yarn build && yarn start-production and open http://localhost:4043/scoped/
    • URL parameters: Run previous release and click around, keep UI open, start new release, reload page
  • UI features (To test: clone microservices demo and run cd deploy/docker-compose && docker-compose up)
    • General: switch between topologies, see nodes and edges, details panel
    • Zoom and pan, switch between topologies
    • Topology filters: namespaces, system containers, etc.
    • Metrics on canvas, try pinning/unpinning
    • Search
      • by container name
      • by usage cpu < 2%
    • Terminal
      • Attach to container to see logs
      • Exec to container and type ls
      • Pop out terminal
    • Contrast mode
    • Download report
    • Pause button

Things to think about

  • ECS Integration
  • Kubernetes Integration
  • CPU and memory usage
Clone this wiki locally