---
robots: noindex, nofollow
tags: pitch
---
For instructions on shaping a project see here: [Shaping a Project](/kX02SXVbS6KzMOQd56i6Cg)

# V8 Bug bash
:snail:
### Problem
How do we validate that v8 is in a releasable state and ensure that we know all the changes in behavior. Additionally how do we make sure that all of that information can be communicated outwards if the changes are intentional.

### Appetite
2 days of bug bashing. The follow up time after the bug bash will take the most time, fixing categorizing, and communicating the various issues that Fluent V8 might have.

### Solution
Test each component looking for the following _when compared to baseline_
* Behavior
* Accessibility/keyboarding
* Appearance
* Dom structure
* HTML Attributes

**TODO**
_Once the testing is complete, we should further divvy out, prioritize, and categorize the various issues to be sure they're fixed in the quickest manner_

### Risks (Rabbit holes)
Perfect is the enemy of good.

### Out of scope (No-gos)
* Bugs that already exist
* It would be nice to fix them, but is not in the scope of the bug bash/validation for v8.