Lagencie
Frequent Contributor
Joined 8 years ago
User Profile
User Widgets
Contributions
Re: NG-Translate hyphenation breaking contentText
yes its a web application, but I do not think that this would help. We are mapping our objects with test-id html attribute so this is not affected, but the problem is the content text which now looks like this for example ... in this case Startup and Reconnection ... and we have some test steps in this case that check for the .contentText of the mapped object and compares those headlines ... but the contentText now is this text with the ­ in the text everywhere. Also if we test textfield inputs / outputs against a database of values for example those run all red now because of this hyphenationNG-Translate hyphenation breaking contentText
Hello, perhaps someone experienced the same problem already - we are using contentText quite often in our testsuite and the developers updated their code lately and they now used the ng-translate hyphenation so that the text get shown better on the UI to the customer. But with this we now have the problem, that many contentTexts now look like the one above "th-is is a co-mp-le-te-ly new te-xt" ... our testing team that uses cypress had a very easy way to adapt their code, as they only added one global function that changes contenttexts with replace("-", "") and it worked again ... but with TestComplete we could for sure do this single step before each use, but we would need to adapt like thousands of teststeps which would take us weeks if not months to adapt.. Is there a way / any setting or something you know in TestComplete that can handle this behaviour? best regards DominikIs there a way to add multiple existence assertions
Hello, I wanted to ask if there is a way - like for example the Smart Assertion - where I can add a single assertion step that checks for 20/30/40 existences of nodes in a response? Currently the only way I see is to rightclick add existence assertion, multiplied by the amount of nodes I have/need. In the Smart Assertion I can only add Assertions on the lowest layer For example here I do not want to test if _master_meta > readPermission > RoleCustomer is valid / true whatever. I want only the master node _master_meta as mandatory, what comes beneath this node does not matter. And if anyhow possible I want to have one single Assertion step, where I can check an example like this where i check the existence of all the 4 nodes, but do not care about what is beneath. Or do I have to create 4 assertions with check for existance of _master_meta, _slave_meta, master and slave?Digest Authentication with X-WWW-Authenticate
Hello, I recently started with ReadyAPI and I got it to work, that it automatically created all my tests I need, but the digest authentication does not want to work. We are not using the standard http response header WWW-Authenticate, but X-WWW-Authenticate - is there a way to manually configure the tool so it makes the digest authentication with this? thats how my current response looks like.
