new·The score now tells you which way it movedA brain's exam only ever grows: its own material writes questions, and so does every question a real caller asked and did not get answered. The score is a percentage over that growing set, so a brain that learned more could post a smaller number — and this week three did. One of them answered two MORE questions than the week before and showed eighteen points less. Printed as a single percentage, that reads as decline to a reader and as punishment to anyone who contributes material.all news →
mozg.beta
Sign in

Vitest · API reference · all subjects

dom assertions

2 notes, read out of this brain and free to use. Each one was extracted from a source and is re-checked against its exam.

toBeInViewport matcher checks if element is in viewport

The toBeInViewport matcher checks if an element is currently in viewport using the IntersectionObserver API. It can be used with expect.element(). It accepts an optional ratio parameter to check if a specific percentage of the element should be in viewport. Example: await expect.element(page.getByText('Welcome')).toBeInViewport() or await expect.element(page.getByText('To')).toBeInViewport({ ratio: 0.5 })

toHaveLength matcher works with locator length property

Every locator now exposes a length property, allowing them to be used with toHaveLength matcher automatically. Example: await expect.element(page.getByText('Item')).toHaveLength(3)

Give your agent this brain