123 results found
-
Exploring Niche Benefits of Open Source Testing Tools for Specialized Applications
While most discussions around open source testing tools focus on general-purpose testing, these tools can offer unique advantages for specialized applications—such as IoT systems, embedded software, or domain-specific platforms. Their flexibility allows engineers to create tailored testing workflows, simulate uncommon scenarios, or integrate with specialized hardware and protocols without being constrained by proprietary solutions.
Additionally, open source tools foster experimentation. Teams can modify source code, build custom plugins, or combine multiple tools to address niche testing challenges. The active community often shares innovative solutions to uncommon problems, giving teams access to insights they might not develop in-house.
For projects requiring…
1 vote -
How Code Coverage Drives Smarter Testing Strategies?
Code coverage is often seen as a simple metric, but its true value lies in guiding smarter testing strategies. Beyond measuring how much of your code is executed during tests, it highlights critical areas that require attention and ensures that important logic paths are not overlooked.
High coverage alone doesn’t guarantee quality—what matters is meaningful coverage. By analyzing which modules, conditions, or decision paths remain untested, teams can prioritize test creation and focus on high-risk areas. Combining code coverage with automated test generation and continuous monitoring helps maintain confidence even as the codebase evolves.
Modern platforms, including Keploy, leverage code…
1 vote -
Hidden Advantages of Open Source Testing Tools
When people talk about open source testing tools, the conversation often revolves around cost savings. While avoiding hefty licensing fees is certainly valuable, there are deeper, often overlooked benefits that make these tools essential in modern software development.
One such advantage is transparency. With open source tools, teams can inspect the code, ensuring there are no black-box components that could affect reliability or security. This is especially important in regulated industries where compliance demands traceability.
Another benefit lies in community-driven innovation. Since anyone can contribute, these tools evolve rapidly, with bugs patched faster and new features introduced in response to…
1 vote -
Add function for server triggers to result in verbose message to user on failure.
Server side triggers currently return 0 for pass, and non-zero for failures. It would be nice to be able to define a table of custom triggerReturnCodes on the server that is retrieved by the client. When a client performs an action that results in a server-side trigger failure the non-zero return code can be used to lookup the error code and provide the user with a more robust message describing the failure.
For example, this robust message could mention pattern restrictions, size requirements, or direct the user to review compliance documents or retrieve crucial developer environment assets/scripts.
1 vote -
ability to comment git on pull requests
it would be awesome if I could add comments on github and bitbucket pull requests right in semanticdiff. it is already possible to fetch pull requests and add comments e.g. with SmartGit, which supports various git backends. Perhaps it would be possible to use their API (if there is one, that is) to add this feature with relatively low cost
3 votes -
A web based gui
Integrate with bitbucket. Will help tremendously with refactored code in pull requests. A web based gui will do the trick I believe
1 vote -
Make Visual Diff more interactive
When comparing files with lots of changes, it would be helpful if the Visual Diff view is more interactive.
For example when you hover an arrow of some moved code (and there are lots of arrows shown), it would be helpful if that arrow gets highlighted, to easily follow the arrow to spot its target.
It would also be helpful if you can show and hide the different items (added, changed, removed, renamed items) that you are either interested in or not interested in (as that removes some complexity from the diff).
3 votes -
Allow export of Visual Diff view content as Image
Sometimes it would be nice to have the possibility to export the complete content of the visual diff window as an image.
The idea behind is to have the complete image (without the need for scrolling) to be able to either print, attach or present it somewhere, or e.g. send it by e-mail.
1 vote -
Build and release as a snap or flatpak package for Linux
Supporting distros is a pain as your repos are very outdated. Just release as a snap or flatpak and have it available everywhere.
1 vote -
1 vote
-
C# timely latest minor version support
It would be really great to have support for the latest minor version of C# in time as a reaction to the fast paced language development.
Otherweise commonly used features lead to annoying parsing errors e.g. the default literal expressions in C# 7.1.
15 votes -
Add more keyboard shortcuts for previous / next diff
Most compare tools support F7 / F8 to navigate through diffs (P4Merge, Araxis)
You should consider adding at least F7 / F8 rather adding complex keyboard configuration in the tool.
Araxis also support by default:
- Ctrl + Page Up, Alt + Left
- Ctrl + Page Down, Alt + Right7 votes -
Disable Oops! We do not support your language... yet!
Would be nice to have the option to disable the dialog as it keeps coming up with known unsupported languages.
E.G. csproj file in VS (just run the text diff)
6 votes -
Support horizontal scrolling with Shift + Mouse wheel / Word wrap option
Sometimes, the diff panels on each file in semanticdiff are too narrow, even when hiding the Semantic Outline. Allowing horizontal scrolling with Shift + Mouse wheel would help reviewing long lines of code. A word wrap option would also do the job, although having both would be the best.
1 vote -
Support for blank comparison
Would be nice if you could start a blank comparison and then copy and paste code from different sources without saving to file like Meld.
4 votes -
Kotlin, please!
Many Android developers are now switching from Java to Kotlin. It could be pretty well to have Kotlin support in SemanticMerge.
9 votes -
Allow external parsers to be configured extension
Semantic Merge allows for external parsers but currently it only allows for one, making the adoption of using them very limited, when you are using more than one non-supported language. I would like it if Semantic Merge could support configuring external parsers by extensions they handle.
3 votes -
Rust support
Rust is a young but promising language. Having semantic merge would be awesome.
3 votes -
semantic merge for better delta code review
how awesome would it be if you join forces with another tool vendor and create a full integration of your semantic diff (including moving things from one file to another) and a tool that helps during code reviews and tracks findings...
finally one could focus on real changesps: plastic scm is missing on their list of integrations
https://smartbear.com/product/collaborator/overview/4 votes -
Show differences highlighted also on the result file
Currently, during a 3-way merge, the individual differences are marked only on the Remote, Base and Local files.
On the Result file, it is only shown the main change (line deleted or added), the individual changes are not shown. For example, if you rename a word in one line, on the 3 source files you have that work highlighted, however, on the result file, it's not highlighted, which makes it hard to see what the difference was.
This would be very useful when solving merge conflicts, because then we could see the differences clearly with the changes on top of…
3 votes
- Don't see your idea?