When to use screen object or component returned by renderPage

[christianacca]

Prior to version 10 of this library, all the examples used the component returned by render method. Now the examples use the screen object.

Both screen and component share the same method names. Questions:

1. for the methods named the same on both objects, is there any functional difference between the them?
2. is it best practice to use screen where possible rather than component

[portothree]

Quoting Kent C. Dodds in Common mistakes with React Testing Library

The benefit of using screen is you no longer need to keep the render call destructure up-to-date as you add/remove the queries you need. You only need to type screen. and let your editor's magic autocomplete take care of the rest.
The only exception to this is if you're setting the container or baseElement which you probably should avoid doing (I honestly can't think of a legitimate use case for those options anymore and they only exist for historical reasons at this point).

[timdeschryver]

A good observation @christianacca !
As @portothree mentioned, we encourage the usage of screen (you should be able to use it everywhere if you're not doing something exotic).
Functionally they both do the same.

[christianacca]

Thanks guys