luckyframework / luckyframework/website

Document testing with `have_error` method

Open
#1,408 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

guides:missing
Dominant language
Crystal
Stars
39
Forks
62
PR merge metrics
No merged PRs in 30d

Description

ref: https://github.com/luckyframework/avram/pull/1062

We could probably create a whole new section for "testing operations" and show how to mock params and all that kind of stuff.

https://luckyframework.org/guides/testing/introduction

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the testing introduction guide and the referenced Avram PR #1062 to understand the `have_error` method and the intended testing examples. Document how to use `have_error`, and confirm whether the proposed testing-operations section should also cover mocking params before expanding the guide.

Written by the indexing model from the issue text.

Assessment

Tech stack
crystal
Domain
documentation, testing
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.