langgenius/dify

[Refactor/Chore] More e2e test

Open

#34.278 aberto em 30 de mar. de 2026

Ver no GitHub
 (11 comments) (1 reaction) (0 assignees)TypeScript (141.412 stars) (22.210 forks)batch import
good first issuestatus: accepting prs🙏 help wanted

Description

Self Checks

  • I have read the Contributing Guide and Language Policy.
  • This is only for refactors or chores; if you would like to ask a question, please head to Discussions.
  • I have searched for existing issues search for existing issues, including closed ones.
  • I confirm that I am using English to submit this report, otherwise it will be closed.
  • 【中文用户 & Non English User】请使用英语提交，否则会被关闭 ：）
  • Please do not modify this template :) and fill in all the required fields.

Description

After #34193, we can add more end-to-end tests to improve stability.

Motivation

No response

Additional Context

No response

Guia do colaborador

Pilha de tecnologia
typescript
Domain
testing
Tipo Issue
test
DifficultyDificuldade de implementação estimada para um novo contribuidor, de 1 para alterações muito pequenas a 5 para trabalho de nível especializado.
3
Tempo estimadoUm intervalo de tempo aproximado para um colaborador experiente investigar, implementar, testar e preparar um pull request.
1-3 hours
Status da atividadeQuão disponível o issue aparece agora: novo, ativo, obsoleto, bloqueado ou aguardando entrada do mantenedor.
active
ClarityCom que clareza o issue explica a mudança esperada, os critérios de aceitação e a próxima etapa.
mostly clear
Prerequisites
end to end testing basicsTypeScriptproject's test setup
Simpatia para novatosUma pontuação de 1 a 100 que estima o quão acessível este issue é para colaboradores iniciantes.
60
Direção de pesquisa
Review PR #34193 to understand the new e2e tests added there. Examine the existing test files in the repository to see the pattern used for e2e tests. Then identify areas of the application that lack test coverage, such as critical user flows, and propose specific tests to add. The maintainers have provided guidance in the comments, so read them for context.