awaldo
Occasional Contributor
Joined 3 years ago
User Profile
User Widgets
Contributions
Re: Name Mapping for Web Elements shared between different pages
My team has switched to a different test suite framework so we're no longer using Test Complete, but it was not implemented before I stopped, and I haven't had any DMs or any other "secret info" since then. If Marsha_R is telling you that it is already implemented, but has not provided you any examples or documentation, then it probably is not implemented, and they just mean "I've given a work-around here, so stop talking about it" With that said, considering it's taken 9 months for anyone else (you) to mention the issue, but takes only days or even minutes for someone to respond with their preferred method, and it seems that the people responding don't even consider it an issue: It seems the general needs and pain points for people are different from ours, or people like us just don't use the TestBear Community, so this is likely considered a "non-issue" for the product, and likely won't get changed. It's just one of the limitations and compromises you get for using a packaged product instead of your team building your own framework. If you love the product otherwise, then I would recommend just accepting this is a trade-off, choosing the work-around that works best for you (I've listed 2 of my own solutions here, and the other responders have a 3rd) and move on. If this is just another in a list of problems getting in the way of your needs, then it might be worth considering using a different test solution that makes compromises that better fit you, or even building your own framework using lower-level tools like TestNG/Selenium if you have the time and expertise.727Views0likes2CommentsRe: Name Mapping for Web Elements shared between different pages
You're right, I misread the wording of their comment and didn't understand what was going on exactly I agree with your assessment though, this is how public forums like this usually work, it's completely normal. I was trying to say something like that in my response as well, that it seems like in general people using this product aren't bothered by the problem like the two of us are and so it's not an issue on the whole. It doesn't exactly help us though, since the proposed solution causes more problems than it's worth, and separating the header elements into a separate project doesn't help us use them in our tests to navigate/login/etc, so it doesn't really help (for my case anyway).710Views1like0CommentsRe: Name Mapping for Web Elements shared between different pages
I do understand the idea behind Projects in a suite. We are already leveraging this by creating separate projects for our different country sites, allowing us to share workflows where they are similar, but specify specific differences for each site. I do not understand how splitting off these header and footer tests into a separate project would be beneficial though. It has the same problems as my solution #1 above as it creates additional copies of the elements anyway, but then also adds additional work in maintenance by worrying about an additional project, and then additional problems outside of the test suite with our pipeline. I don't see what we actually gain from this solution that we do not using my proposed workaround #1, and I do see more tradeoffs in implementing it.1.1KViews0likes0CommentsRe: Name Mapping for Web Elements shared between different pages
I hope that kind of solution works well for you, but for me it honestly just sounds worse than the other options. I don't really see how this solution would be an improvement on any of our problems, other than being a bit less cluttered in the NameMapping tree. Creating a new project would then de-couple the header and footer from our normal testing entirely, even more strongly than the #1 option I already thought of. That means when we have to change out our site design, we now have an additional project to remap entirely, not just a set of NameMapping entities. It would be slightly simpler to look at, but more work on maintenance, and then creates awkward decisions for our automated pipeline, requiring us to run 2 (or more if we take this approach to every shared item we add) different run jobs, which complicates our logic, and adds more projects to maintain and monitor.1.1KViews0likes2CommentsName Mapping for Web Elements shared between different pages
I am attempting to automate a test case we have that involves verifying that the Header and Footer elements of our site are present, and work on all of our pages. The problem I am having is that in the NameMapping, the individual web elements can only be tied directly as a child to a single Page object. From what I've read and experimented with, this leaves us with only 2 options: 1) Duplicate the header and footer mappings for every, single, page. 2) Create a wildcard page (https://ourwebsite.com*) and putting the elements in that page entry The problem with #1 is that none of the individual items are in any way linked or referenced to eachother, so if there are any changes to the shared element(s), then we would have to go and change every single one instead of just in once place, which could be decently common considering we revamp our site look more than once a year. Right now this would be a nuisance, but will actually cost us considerable time in the future as we expand our test coverage and the site gets more modernized and we keep adding shared web elements like a chat helper, notification modals, login/account segment, etc. The problem with #2 is that creating a wildcard for the entire website means that Every object recording we would do in the future would automatically be assigned to that wildcard page in the NameMapping instead of the specific pages they belong to, which then just adds an additional step for us to go in and relocate every recorded object where they need to go to avoid an overcluttered mess. Is there a more intentionally designed way to do this behavior instead of these hacks? I feel like this should be an extremely common use case with modern website design.Re: Sharing name mappings between page objects when several pages have elements in common
I am also finding myself with the same question. Modern web development is FULL of shared web elements like headers, footers, menus, "can we help you" chatboxes, etc. It seems strange to me that there does not seem to be a dedicated solution to handle this, and no-one seems to have a good answer as to how to do it even non-simply702Views0likes0Comments