remove beta-test tests

behat.yml

@@ -27,7 +27,6 @@ default:
 #        - '%paths.base%//features//Sp2Idp2Sp1Idp2Sp3.feature'
 #        - '%paths.base%//features//Sp3Idp1Sp1Idp1Sp2Idp2.feature'
 #        - '%paths.base%//features//WwwMetadataCept.feature'
-#        - '%paths.base%//features//ZSp1Idp1BetaSp1Idp3.feature'
     status_features:
       paths:    [ '%paths.base%//features//status.feature' ]
       contexts: [ 'StatusContext' ]

dockerbuild/run-tests.sh

@@ -9,6 +9,5 @@ set -e
 /data/run-metadata-tests.sh
 
 ./vendor/bin/phpunit -v tests/AnnouncementTest.php
-./vendor/bin/phpunit -v tests/IdpDiscoTest.php
 
 /data/run-integration-tests.sh

docs/the_hub.md

@@ -21,13 +21,6 @@ It is also used by the `TagGroup.php` Auth Proc to convert group names into the
 
 `idp|<IDPNamespace>|<group name>`.
 
-##### betaEnabled
-An optional metadata entry is `betaEnabled`.  
-This will allow the IdP to be marked as `'enable' => true` when the user has a certain cookie ('beta_tester') that they would get from visiting `hub_domain/module.php/sildisco/betatest.php`.  
-The user would need to manually remove that cookie to be free of this effect.
-
-Sildisco does not otherwise deal with looking at the `'enable'` value.  However, a theme for idp discovery may (e.g. simplesamlphp-module-material).
-
 ##### SPList
 In order to limit access to an IdP to only certain SP's, add an `'SPList'` array entry to the metadata for the IdP.  The values of this array should match the `entity_id` values from the `sp-remote.php` metadata.