End-to-end cases of the admin left out of the first harness

Abierto
#3,213 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
csharp

Línea de trabajo

Start with the end-to-end harness from #3149 and the review of #3206, then trace the account page work in #3147 and the IFormDraftStore flow in A2. Add the listed browser cases, including secret redaction checks for authenticator keys and recovery codes. Done means each case is covered and the sensitive account steps are excluded from kept traces.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

area:admin area:testing type:feature

The end-to-end harness of #3149 covers sign-in, sign-out, a session the server ends, two tabs, the sidebar and the site switch. These browser cases of #3149 and of its first comment are not covered and are tracked here:

  • The form draft is kept across an expired session and restored after the new sign-in (waits for a page that uses IFormDraftStore, in A2). (#3242)
  • Sign-out asks first when a form has unsaved changes (same). (#3246)
  • Back after sign-in does not replay the callback; a failed or reloaded callback shows the error state and a way to start again.
  • A logout the user does not confirm on the hosted page leaves the admin signed in.
  • sessionStorage blocked: the admin says so instead of looping.
  • A user who must change its password, and one whose role requires two-factor, are sent through the hosted pages and come back.
  • An endpoint that hangs: the admin's bounded waits end with a message.
  • Two tabs past the server's 30-second reuse leeway of a refresh token.
  • The account page (#3147): sessions listed and one ended, two-factor enrolment with a code computed from the shown key, recovery codes shown once, disable; an external login removed; the password change link and its return. Before these are written, the trace handling must cover secrets that no pattern matches: the authenticator key and the recovery codes appear in screenshots and in snapshot text, so the run's literal values are checked and screenshots of those steps are left out of a kept trace.

From the review of #3206.

Lenguaje dominante
C#
Estrellas
567
Forks
107
Merge medio
1 h 19 min
PR fusionados (30 d)
353

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de fluentcms/FluentCMS

Todos los issues de fluentcms/FluentCMS

Issues similares

Más issues de C#

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.