Top Tweets for #reactnativetestinglibrary
πΌ React Native Developer at Apexon
π United States
π οΈ #reactnative #javascript #es6plus #redux #mobx #contextapi #swift #objectivec #java #kotlin #jest #reactnativetestinglibrary #eslint #git #ios #android
π https://t.co/6CLBc2rvWm
π¦ Using @jotaijs state management and want to test it with #ReactNativeTestingLibrary? Weβve got you covered!
@vanGalilea has written a Cookbook recipe just for this case π
Check it out and make your testing smoother!
https://t.co/2yFGsTJezv
π¦ I've just published the 2nd recipe for the #ReactNativeTestingLibrary Cookbook π
π‘ It explain when, why and how to use async tests when using RNTL
https://t.co/j7p2QDF3uG

The 1οΈβ£st #ReactNativeTestingLibrary Cookbook recipe is here: custom render functions. πβ¨
Join the effort and share your favourite recipes through our GH repo. ππ©βπ»π¨βπ»
π Read more: https://t.co/57Cs1ibmz9
π Announcing the #ReactNativeTestingLibrary Cookbook initiative! πβ¨
We're compiling best practices, tips & tricks, and ready-to-use recipes for the RNTL community. π²π©βπ»π¨βπ§
Got a recipe to share? Contribute and help us create something amazing! π
π More details: https://t.co/EYO4TcA3Ii
βοΈπ¦ When using #ReactNativeTestingLibrary, I use this query as a default:
getByRole("role", { name: "name" })
Here's why:
πΉ get - I want exactly one matching element
πΉ byRole + name - I want to get an element matching both a role (e.g., "button") and a name (e.g., "Next")

βοΈπ¦ #ReactNativeTestingLibrary with ver. 12.4.0 has achieved its main dev goals:
πΉ Introduction of User Event API
πΉ Migration of Jest matchers to RNTL
π We do not plan more large features in v12.
π Our next focus will be improving the documentation and examples.
βοΈπ¦ #ReactNativeTestingLibrary tip.
If your query cannot find an element:
1οΈβ£ Use screen.debug() to inspect the element tree
2οΈβ£ Use `includeHiddenElements: true` query option to detect hidden elements.
https://t.co/PM2N2ZL3Kn
βοΈπ¦ In #ReactNativeTestingLibrary each query consists of two key components:
πΉ Variant: `get`, `query`, ...
πΉ Predicate: `*ByRole`, `*ByText`, ...
π‘Predicate describes the specific criteria used to find matching elements.
π Quick summary of available predicates:

βοΈπ¦ Using proper #ReactNativeTestingLibrary query variants helps to better express the test's intent.
π‘ Query variants also serve as implicit assertions on number of matched elements.
π General guidelines for idiomatic query variants:


βοΈ #ReactNativeTestingLibrary v12.3.1 is out!
Highlights:
π UserEvent scrollBy API for better simulation of ScrollView interaction
π¦ Improved fake timer handling for UserEvent press and other interactions
https://t.co/VFKqBy1nGe
BTW We've released #ReactNativeTestingLibrary v12.3.0 yesterday, just in time for #ReactNativeEU β€οΈπ«Ά
It provides support ARIA web accessibility props (role & aria-*) π
https://t.co/2s7i81xFkz

π‘ #ReactNativeTestingLibrary #TipOfTheDay
Most of RNTL queries accept TextMatch = string | RegExp as first argument.
RegExp is the flexible option while string matcher uses case-sensitive full string equality by default. You can enable case-insensitive substring matching using the { exact: false } option.
This is relevant for most of the RNTL queries:
- getByRole
- getByText
- getByLabelText
- getByHintText
- getByPlaceholderText
- getByDisplayValue
- getByTestId

Despite summer heat βοΈπ₯ #ReactNativeTestingLibrary is more active than ever π
I've just landed a new API proposal for Jest Native matches migration to RNTL repo. Join the discussion and learn about issue we plan to solve π¬π
https://t.co/lLgpVHJ3tJ
πͺ Ever wanted to contribute to an Open Source project?
I've created some relatively easy tasks for #ReactNativeTestingLibrary Jest Native matchers migration that could get you on track with that:
https://t.co/KoIjP2a1Fj
I've create a #ReactNativeTestingLibrary API proposal for User Event scroll interaction.
π¬ Join the discussion to help us decide on the best API π
https://t.co/eqV9aLwFDy
π‘π» Just released #ReactNativeTestingLibrary v12.2.1!
It fixes a small omission from the initial User Event API:
β³οΈ clear() function for clearing the content of a TextInput
π‘ UserEvent type() function appends text to given TextInput, so you need to call clear() to actually replace it.

π‘ #ReactNativeTestingLibrary #TipOfTheDay:
In order for *ByRole queries to work, the matched element needs to be an accessibility element.
When element is accessibility element?
1. Text, TextInput and Switch are these by default
2. Host View needs to have accessible prop set
3. Some RN components like Pressable & TouchableOpacity automatically render host View with accessible prop
This matches RN + iOS/Android runtime behavior, where Views without accessible prop are ignored by screen reader.
π

Last Seen Hashtags on Sotwe
TaxLawImpact
Seen from United States
θ€εζ―εΈ
Seen from United States
MVSales
BlueCop
Seen from Puerto Rico
sellingcontent
Seen from Brazil
vinicolaitaliana
Seen from Brazil
incestkink
Seen from Brazil
momson ()
Seen from United States
onlyforfantasy
Seen from Indonesia
FueraDirigente
Seen from Brazil
Most Popular Users

Elon Musk 
@elonmusk
240.1M followers

Barack Obama 
@barackobama
119.3M followers

Donald J. Trump 
@realdonaldtrump
111.6M followers

Cristiano Ronaldo 
@cristiano
108.7M followers

Narendra Modi 
@narendramodi
106.9M followers

Rihanna 
@rihanna
97.2M followers

NASA 
@nasa
92.1M followers

Justin Bieber 
@justinbieber
90.5M followers

KATY PERRY 
@katyperry
86.7M followers

Taylor Swift 
@taylorswift13
80.5M followers

Lady Gaga 
@ladygaga
72.1M followers

Kim Kardashian 
@kimkardashian
69.3M followers

YouTube 
@youtube
68.6M followers

Virat Kohli 
@imvkohli
68.4M followers

Bill Gates 
@billgates
63.4M followers

The Ellen Show
@theellenshow
62.5M followers

CNN 
@cnn
61.9M followers

Neymar Jr 
@neymarjr
60.9M followers

X 
@x
60.9M followers

CNN Breaking News 
@cnnbrk
59.9M followers


