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

オープン
#3,213 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
35/100
issue の種類
機能追加
明瞭さ
おおむね明確
活発さ
活発
技術スタック
csharp

調査の方向性

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.

索引モデルが issue の本文から書いたものです。

説明

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.

主要言語
C#
スター
567
フォーク
107
平均マージ
1時間 19分
マージ済み PR(30日)
353

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

fluentcms/FluentCMS のほかの issue

fluentcms/FluentCMS の issue をすべて見る

似ている issue

C# の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。