George Kalpakas 04ab5edf65 test(docs-infra): correctly test URL redirects when the destination URL is also redirected (#42018) ... Since #41625, `/guide/updating-to-version-10` is being redirected to `https://v11.angular.io/guide/updating-to-version-11`. However, `v11.angular.io` itself is being redirected to `angular.io`, while v11 is the latest stable version. As a result, `/guide/updating-to-version-10` ends up being redirected to `https://angular.io/guide/updating-to-version-11`. Currently, this causes a CI failure in the `aio_monidoting` job ([example failure][1]). This will change once v12 is released as the new stable version. Alternatively, we could update the config and tests to expected `/guide/updating-to-version-10` to be redirected to `https://angular.io/guide/updating-to-version-11`, but that would end up being redirected to `https://angular.io/guide/updating-to-version-12` once v12 would be released, which is different behavior. This commit provides a way to test for redirects when the destination URL is itself redirected to a different URL. This allows us to use the intended URL (for example, `https://v11.angular.io/...`), which will continue to work as expected regardless of what is the latest stable version without causing CI failures. [1]: https://circleci.com/gh/angular/angular/983738 PR Close #42018		2021-05-20 16:07:59 +00:00
..
deployment	test(docs-infra): correctly test URL redirects when the destination URL is also redirected (#42018)	2021-05-20 16:07:59 +00:00
e2e	feat(docs-infra): improve search query processing (#41368)	2021-04-01 12:02:37 -07:00