Recorder module produces messy repository
Posted: Thu Oct 19, 2017 8:53 am
Hi,
I have a colleague that doesn't have the coding experience to create tests with C# or manually build a repository with good Xpath queries.
So instead, the person is trying to use the recording module exclusively.
But the thing is, the repository that the recorder generates is messy. Like, super messy.
It puts in a bunch of ? and // and generally flattens the repo in a way that makes it unreadable and unreliable. Some containers that it generates incorrectly matches other containers because the path and properties it generates are too generic (so when you try to play the recording, it fails).
Is there some setting that tells the recorder to generate a nicer repository ? (something closer to the structure seen in the Spy app?)
I have a colleague that doesn't have the coding experience to create tests with C# or manually build a repository with good Xpath queries.
So instead, the person is trying to use the recording module exclusively.
But the thing is, the repository that the recorder generates is messy. Like, super messy.
It puts in a bunch of ? and // and generally flattens the repo in a way that makes it unreadable and unreliable. Some containers that it generates incorrectly matches other containers because the path and properties it generates are too generic (so when you try to play the recording, it fails).
Is there some setting that tells the recorder to generate a nicer repository ? (something closer to the structure seen in the Spy app?)