Espresso ViewMatchers.withText doesn't work when textAllCaps is enabled [72798625]

Fixed

Bug

[AOSP] assigned

Status Update

No update yet.

Description

ra...@gmail.com

created issue #1

Feb 1, 2018 12:05PM

Library used (Espresso, Runner, Rules etc.):
Version used: 3.0.1

What steps will reproduce the problem?
1. Put an AppCompatTextView in your UI with android:textAllCaps="true" and android:text="Low Stock" in your XML (I'm using android:id="@+id/lowStockTV")
2. Launch your activity through a Test. AppCompatTextView will be shown as "LOW STOCK"
3. Check that that view has text with Espresso in the following way:

onView(withId(R.id.lowStockTV))
.check(
matches(withText("LOW STOCK"))
)

How are you running your tests (via Android Studio, Gradle, adb, etc.)? Android Studio

What is the expected output?
The expected output is obtaining a valid ViewInteraction with no throw (AssertionFailedWithCausedError)

What do you see instead?
AssertionFailedWithCausedError with message:

'with text: is "LOW STOCK"' doesn't match the selected view.
Expected: with text: is "LOW STOCK"
Got: "AppCompatTextView{id=2131296406, res-name=lowStockTV, visibility=VISIBLE, width=1002, height=57, has-focus=false, has-focusable=false, has-window-focus=true, is-clickable=false, is-enabled=true, is-focused=false, is-focusable=false, is-layout-requested=false, is-selected=false, layout-params=android.widget.LinearLayout$LayoutParams@5155c10, tag=null, root-is-layout-requested=false, has-input-connection=false, x=39.0, y=39.0, text=Low Stock, input-type=0, ime-target=false, has-links=false}"

if I use:
onView(withId(R.id.lowStockTV))
.check(
matches(withText("Low Stock"))
)

it works perfectly, I get my ViewInteraction, but that's not why I see in my UI

Comments

gg...@google.com <gg...@google.com> #2Feb 2, 2018 09:38AM

Assigned to gg...@google.com.

this would be nice but given Compose and all other priorities, we are not planning to make any big investments in data binding (support KSP is a very big task).

ra...@gmail.com <ra...@gmail.com> #3Feb 2, 2018 10:16AM

Makes sense. And is there any way to trigger data binding without kapt plugin, assuming there are no custom binding adapters in given module?

gg...@google.com <gg...@google.com> #4Feb 7, 2018 07:25AM

unfortunately no. data binding still needs to be able to read your code and annotation processing is the only API that allows us to do it :(

gg...@google.com <gg...@google.com> #5Apr 19, 2018 10:27AM

Marked as fixed.

It's a very disappointing decision for many projects who heavily depend on data binding, which will never be able to get rid of all bindings code and especially rewrite all UI to Compose.

It means that bindings are essentially deprecated

ni...@gmail.com <ni...@gmail.com> #6Jan 16, 2019 06:13PM

It does not mean data binding is deprecated unless KAPT is deprecated (if that happens, we would need to support KSP).Unfortunately, moving data binding to KSP is a large order so it makes more sense to keep focusing on KAPT than rewrite data binding.

We might re-consider this in the future based on KSP becoming stable, Compose adoption and KAPT stability but it is very unlikely to happen.

dy...@gmail.com <dy...@gmail.com> #7Jan 27, 2019 10:39PM

KSP is now stable stage.
https://android-developers.googleblog.com/2021/09/accelerated-kotlin-build-times-with.html

Can google reconsider to adapt KSP on databinding compiler?

dy...@gmail.com <dy...@gmail.com> #8Jan 27, 2019 10:41PM

Unfortunately this is still a NO for 2022 planning due to reasons mentioned in #2.

theme-for-ios-11.apk

25 MB

Download

[Deleted User] <[Deleted User]> #9Mar 31, 2021 09:32PM

kapt seems no longer adding new feature

kapt is in maintenance mode. We are keeping it up-to-date with recent Kotlin and Java releases but have no plans to implement new features. Please use the Kotlin Symbol Processing API (KSP) for annotation processing. See the list of libraries supported by KSP.

https://kotlinlang.org/docs/kapt.html

So this mean databinding will also deprecated or will be support KSP?

co...@gmail.com <co...@gmail.com> #10Dec 12, 2024 10:11AM

Databinding is in maintenance mode as well.
We don't plan to support KSP nor recommend data binding usage at this stage since compose is our recommended UI solution.

ma...@gmail.com <ma...@gmail.com> #11Jan 20, 2025 12:30AM

We don't plan to support KSP nor recommend data binding usage at this stage since compose is our recommended UI solution.

I have been waited this answer in several years.

Because it is an important basis to convince co-workers and for determining the technology stack of an app.

zh_default_se.pth

1.7 KB

Download

ma...@gmail.com <ma...@gmail.com> #12Jan 20, 2025 09:49AM

Databinding is in maintenance mode as well.

We don't plan to support KSP nor recommend data binding usage at this stage since compose is our recommended UI solution.

A bit of a tangent here, but what about ViewBinding? Will that one stay going strong or will it fade along with DataBinding?

ma...@gmail.com <ma...@gmail.com> #13Jan 20, 2025 09:49AM

ViewBinding is only a build tool and does not run an annotation processor, hence it is not impacted by KAPT / KSP.

So if you are using Views, ViewBinding will keep working.
It is the same for Data Binding as well though. The main difference is that if KAPT stops working, DataBinding will stop working whereas ViewBinding will keep working. Hopefully, any such situation will be far enough that no-one will care and everyone will be using Compose :)