Forum Discussion
Running into similar situation awaldo did you find any solution to this because what Marsha_R is trying to tell is already implemented in my case and I can't distribute it more.
- awaldo2 years agoOccasional Contributor
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.
- Marsha_R2 years agoChampion Level 3
Hi @awaldo
If you reread the post from larebshaikh, you'll see that they are saying they have already implemented what I suggested, not that I said anything was implemented nor that I am hiding anything. Since I don't work for SmartBear, I would not be the first one to hear about changes anyway. I have, however, seen items on the Feature Requests list be implemented.
The behavior you described in the posts is what normally goes on here. Volunteers like rraghvani and I spend time on the forums to offer our expertise and we are happy to keep discussing issues, with no "stop talking about it" implied. What usually happens, even if we try to follow up, is that the original poster disappears.
If the workarounds are not sufficient to keep the user's work progressing, then there is always the option of logging an issue with Support.
I think you will find that most testing teams have different requirements and different environments and no one is testing anything exactly the way or for the same purpose as anyone else. They will also choose tools and design tests that fit them the best.
I wish you luck in testing with your new framework.
- awaldo2 years agoOccasional Contributor
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).
Related Content
- 6 years agopaulohg6