Sha256: 2a2eb3fe9d1c8d38c90cded0e7dcfc0286da35984573b7fa63aa996c08606b7f

Contents?: true

Size: 959 Bytes

Versions: 2

Compression:

Stored size: 959 Bytes

Contents

@lb_test

Feature: PHP Server Templates
  Tests the PHP servers

Scenario: PHP server test

  Given A frontend with application servers deployment
  Then I should stop the servers
  Then I should set a variation for connecting to shared database host

  When I launch the "Front End" servers
  Then I should wait for the state of "Front End" servers to be "booting"
  Then I should wait for the state of "Front End" servers to be "operational"
  Then I should set a variation LB_HOSTNAME
  When I launch the "App Server" servers
  Then I should wait for the state of "App Server" servers to be "booting"
  Then I should wait for the state of "App Server" servers to be "operational"
  Then I should cross connect the frontends

  Then I should run unified application checks
  Then I should run frontend checks
  Then I should run log rotation checks

  Then I should test reboot operations on the deployment

  Then I should check that monitoring is enabled

Version data entries

2 entries across 1 versions & 1 rubygems

Version Path
virtualmonkey-0.0.1 features/old_cuke_features/php.feature
virtualmonkey-0.0.1 features/old_cuke_features/tomcat6.feature