For completeness only (and because Member Expressions may cause the request to fail)
As @existdissolve stated that you can archive something like this (not the same thing!) As a wildcard using the Member Expression expression in your case
Ext.ComponentQuery.query('button > menu > menuitem{text.search("Welcome")!=-1}');
This will attempt to perform its own JS lookup operation in the text property of any menu item found. Regardless of whether this property (or method) exists that leads me to the main problem of member expressions
What you need to know about Member expressions
You can use member expressions for almost every selector, but they need to exist in that selector, or you will get an exception that interrupts the request (completely, as the exception does).
Here is a simple example. Let's say you want to find text on it. This should not be a problem, all buttons need text, right? This works for quite some time, until your client complains that some buttons do not need text, a simple image is enough. You forgot about the request and added a button, and suddenly parts of your application stopped working while you ended up with an exception, for example
Uncaught TypeError: Unable to call the search method undefined
You can try it yourself in this JSFiddle . Try "find me" and then click the "add image" button and try again.
Why is this happening? The Ext.ComponentQuery test Ext.ComponentQuery if the property exists and an expression does not exist that can quickly lead to a general request failure.
Yes, the above example is simple, and you can find the source of the error very quickly, but it can also be completely different.
Now what? I do not mean to say that you should not use the expression Member, but you really need to take care of those side effects that you may encounter.