"Wait for 'class' attribute 'Contains' value" fails with an unexpected error if the step converted to code

Hello Daria,

Thank you for contacting us with this scenario and for sharing details about the encountered behavior. 

I have to say that the converted Wait for attributes step does not work in the same way as the recorded one. This is because the recorded steps and the Test Studio UI manage elements in a slightly different way than on the Framework level. Once the step is converted to code, we only give guidance and references to the elements, but this implementation needs to be handled by the QA engineer or the developer of the test.

The issue comes from the wait part of the verification in the process of getting the attributes. Specifically when there is no such element on the page. There are two ways to go forward with this. 

1. Use the originally recorded "Verify attribute contains" step and do not change its role to Wait step. For further customization of the test scenario, you can convert it to code and it will work as expected.
2. If you need to wait for the element with specific attribute to appear in the DOM tree in a coded step, you can use the code sample below. It will wait for the target element to appear (in this case 30000 msec) and assert the specified attribute. Notice that I do not rely on elements from Pages and it is good practice to always initialize the elements that the code uses. The sample code uses an element from www.google.com page.
   

               var element =  this.ActiveBrowser.WaitForElement(30000, new string[]{ "tagname=a", "textcontent=Gmail"});
               Assert.IsNotNull(element);
               string attribute = element.GetAttribute("class").ToString();
               Assert.AreEqual("lorem ipsum", attribute);

Please check out the above suggestions and let me know if that solves the issue you were having. I remain available to continue our discussion and advise you further.

Regards,
Plamen Mitrev
Progress Telerik