# Blog Post: Some Elixir Testing Tricks

**URL:** <https://forum.elixirforum.com/t/blog-post-some-elixir-testing-tricks/56524>\
**Category:** Blog Posts\
**Tags:** testing, via-devtalk, blog-post, blogs-by-paradox\
**Created:** [June 15, 2023, 1:06pm UTC](https://forum.elixirforum.com/t/blog-post-some-elixir-testing-tricks/56524 "2023-06-15T13:06:38Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![Paradox](https://forum.elixirforum.com/user_avatar/forum.elixirforum.com/paradox/32/30928_2.png) [@Paradox](https://forum.elixirforum.com/u/Paradox)\
**Post date:** [June 17, 2023, 12:50am UTC](https://forum.elixirforum.com/t/blog-post-some-elixir-testing-tricks/56524/8 "2023-06-17T00:50:04Z")

</div>

I’ve written and used similar macros before. One thing that I’ve seen some do, and have mixed feelings about, is directly grabbing the `lv` variable from the calling site. This is nice because it lets you write really compact tests

```elixir

click("Edit Profile")

assert_view("h1", "Editing profile")

```

But the downside is that they’re “magical,” they grab the LV or HTML out of their call site with no apparent way of doing so to the caller. Depending on your teams proficiency and feeling towards this, it can be a major downside.

I’m gonna collect some more of these tips into a second article 😄

---

_[View the full topic](https://forum.elixirforum.com/t/blog-post-some-elixir-testing-tricks/56524)._