Тестирование функции
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 48/100
Research direction
Start by locating the user creation or save entry point and any existing test project in the repository. Add unit coverage for rejecting an empty password with the stated error, and clarify the expected result for a duplicate login before testing that case. Run the repository's test command and confirm both scenarios pass.
Written by the indexing model from the issue text.
Description
Юнит-тесты
-
проверяем, что пользхователь с пустым паролем не сохраняется в систему.
Выдается ошибка: задайте не пустой пароль -
проверяем, что добавляемый пользователь с таким логином существует
- Dominant language
- C#
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from testAlexB/ConsoleApp2
-
Разработка функцииOpen
Difficulty 5/5 Over a week Newbie friendliness 20/100
testAlexB/ConsoleApp2#2 ·
-
Difficulty 5/5 Over a week Newbie friendliness 15/100
testAlexB/ConsoleApp2#1 ·
All issues in testAlexB/ConsoleApp2
Similar issues
-
area/navigationview 🧭 difficulty/starter 🚀 good first issue kind/bug platform/all project/navigation-lifecycle 🧬 triage/untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
unoplatform/uno#24925 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
DamianEdwards/ghcp-spend-tray#39 ·
Maintainers usually reply within 1 day
-
copilot documentation
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 2 days
-
[Rust][Flaky Test] multiple_deadlines_fire_in_order asserts a wall-clock gap instead of firing orderOpenCI/CD ⚒️ Flaky-tests 🐦
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
valkey-io/valkey-glide#7255 ·
Maintainers usually reply within 3 days
-
bug good first issue
Difficulty 1/5 Under an hour Newbie friendliness 92/100
unoplatform/Uno.Core#99 ·