Alternatives to QMetry logo

Alternatives to QMetry

Zephyr, FitNesse, Testrail, Selenium, and qTest Management are the most popular alternatives and competitors to QMetry.
16
34
+ 1
0

What is QMetry and what are its top alternatives?

QMetry is a comprehensive test management tool that helps in managing the testing of software applications throughout the development lifecycle. It offers features such as test case management, test planning, test execution, traceability, and reporting. However, some limitations of QMetry include a steep learning curve for new users and the lack of integration with certain popular tools.

  1. TestRail: TestRail is a test management tool that allows teams to organize and manage their testing efforts efficiently. Key features include test case management, test runs and plans, reporting, and integrations with popular issue tracking tools. Pros include a user-friendly interface and easy customization options, while a con could be the cost for smaller teams.

  2. Zephyr: Zephyr is a test management tool designed to help teams plan, manage, and execute their testing efforts. It offers features like test case creation, test execution, reporting, and integration with various automation tools. Pros include seamless Jira integration and an intuitive interface, while a con could be the complexity of setting up certain features.

  3. PractiTest: PractiTest is a test management platform that provides end-to-end testing solutions for QA and development teams. Key features include requirements management, test design, test execution, and integrations with various tools. Pros include customizable dashboards and advanced reporting capabilities, while a con could be the pricing for larger teams.

  4. TestLink: TestLink is an open-source test management tool that helps in organizing test cases, tracking test results, and managing test projects. It offers features like test plan management, requirements tracking, and test reports generation. Pros include being free and open-source, while a con could be the lack of advanced features compared to commercial tools.

  5. Xray: Xray is a test management tool designed for Jira users, offering features like test case management, test execution, and reporting. Pros include seamless integration with Jira and flexible test design options, while a con could be the learning curve for new users.

  6. Katalon Studio: Katalon Studio is a test automation tool that also offers test management capabilities. It provides features like test case design, test execution, reporting, and integration with various third-party tools. Pros include all-in-one testing solution and easy integration with Katalon Automation Recorder, while a con could be the limited customization options.

  7. PractiTest: PractiTest is a comprehensive test management platform that offers end-to-end testing solutions for QA teams. Key features include test case management, requirements coverage, test execution, and integrations with various tools. Pros include customization options and advanced reporting capabilities, while a con could be the pricing for larger teams.

  8. Qase: Qase is a modern test management tool that helps teams organize and manage their testing efforts efficiently. It offers features like test case management, test execution, reporting, and integration with popular CI/CD tools. Pros include a simple and intuitive interface, while a con could be the limited customization options.

  9. Test Collab: Test Collab is a test management tool designed to help teams plan, execute, and track their testing efforts effectively. It offers features like test case management, test execution, reporting, and integration with various automation tools. Pros include a user-friendly interface and affordable pricing, while a con could be the lack of advanced customization options.

  10. TestLodge: TestLodge is a test management tool that allows teams to manage their testing efforts easily. Key features include test case management, test plans, test execution, and integrations with popular issue tracking tools. Pros include a simple and straightforward interface, while a con could be the limited reporting capabilities.

Top Alternatives to QMetry

  • Zephyr
    Zephyr

    Manage all aspects of software quality; integrate with JIRA and various test tools, foster collaboration and gain real-time visibility. ...

  • FitNesse
    FitNesse

    It is an open source project. The code base is not owned by any company. A lot of information is shared by the FitNesse community. It's extremely adaptable and is used in areas ranging from Web/GUI tests to testing electronic components. ...

  • Testrail
    Testrail

    TestRail helps you manage and track your software testing efforts and organize your QA department. Its intuitive web-based user interface makes it easy to create test cases, manage test runs and coordinate your entire testing process. ...

  • Selenium
    Selenium

    Selenium automates browsers. That's it! What you do with that power is entirely up to you. Primarily, it is for automating web applications for testing purposes, but is certainly not limited to just that. Boring web-based administration tasks can (and should!) also be automated as well. ...

  • qTest Management
    qTest Management

    It is a test management software used by the small as well as large-scale organization. It helps to create a centralize test management system for easy communication and rapid deployment of the task to QA teams and developers. ...

  • Cucumber
    Cucumber

    Cucumber is a tool that supports Behaviour-Driven Development (BDD) - a software development process that aims to enhance software quality and reduce maintenance costs. ...

  • JavaScript
    JavaScript

    JavaScript is most known as the scripting language for Web pages, but used in many non-browser environments as well such as node.js or Apache CouchDB. It is a prototype-based, multi-paradigm scripting language that is dynamic,and supports object-oriented, imperative, and functional programming styles. ...

  • Git
    Git

    Git is a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency. ...

QMetry alternatives & related posts

Zephyr logo

Zephyr

60
112
1
A real-time Test Management solution
60
112
+ 1
1
PROS OF ZEPHYR
  • 1
    Good integration with JIra
CONS OF ZEPHYR
  • 3
    Slow UI
  • 2
    Slower performance
  • 2
    Lack of debugging insights
  • 2
    Lack of bulk edit operations for test runs
  • 2
    Doesn’t add much value to non-Jira users

related Zephyr posts

Shared insights
on
JiraJiraZephyrZephyrQMetryQMetry

could you please share any pros and cons of QMetry compared to Zephyr? The team is already using Jira and needs a tool for test management integrated into Jira. tks

See more
FitNesse logo

FitNesse

30
60
0
The fully integrated standalone wiki and acceptance testing framework
30
60
+ 1
0
PROS OF FITNESSE
    Be the first to leave a pro
    CONS OF FITNESSE
      Be the first to leave a con

      related FitNesse posts

      Testrail logo

      Testrail

      197
      259
      30
      Efficiently manage, track and organize your software testing efforts
      197
      259
      + 1
      30
      PROS OF TESTRAIL
      • 10
        Designed for testers
      • 6
        Easy to use
      • 5
        Intutive
      • 5
        Easy Intergration
      • 3
        Customer Support
      • 1
        Integration to jira
      CONS OF TESTRAIL
      • 4
        Pricey

      related Testrail posts

      Shared insights
      on
      TestrailTestrailmablmabl

      Hello everyone!

      Need your advice in my new company. I am new to this website as well. Any thoughts on what TCM we can use if we have mabl Automation to have not big total expenses? Or to change the automation framework and get TCM.

      I used Testrail ($1-2k) as TCM but expenses are quite big in total with Mabl ($1k) . The product has lots of visual content such as diagrams, graphics, and tables where data displayed from 1 big table. Company is using Mabl for Automation. There are not so much Backend tests. Frontend is not covered and no started.

      I am looking for TCM to start creating TCs for manual testing, then want to highlight tests for regression and automate them. Also team ready to automate Backend as well.

      See more
      Shared insights
      on
      Visual StudioVisual StudioTestrailTestrail

      I have used Testrail for several years but my company is switching to Devops for everything (including QA/Testing). We are dropping TestRail because of the cost. TestRail is, overall, a better tool for QA. Devops is very tedious for test plan/suite/case creation. Actually executing a test is pretty good, But writing / creating the plans are pretty cumbersome. I have requested a few improvements through the Visual Studio community but I don't have high hopes. I just don't think enough QAs are using Devops. Is anybody else in this boat?

      See more
      Selenium logo

      Selenium

      15.5K
      12.4K
      526
      Web Browser Automation
      15.5K
      12.4K
      + 1
      526
      PROS OF SELENIUM
      • 176
        Automates browsers
      • 154
        Testing
      • 101
        Essential tool for running test automation
      • 24
        Record-Playback
      • 24
        Remote Control
      • 8
        Data crawling
      • 7
        Supports end to end testing
      • 6
        Easy set up
      • 6
        Functional testing
      • 4
        The Most flexible monitoring system
      • 3
        End to End Testing
      • 3
        Easy to integrate with build tools
      • 2
        Comparing the performance selenium is faster than jasm
      • 2
        Record and playback
      • 2
        Compatible with Python
      • 2
        Easy to scale
      • 2
        Integration Tests
      • 0
        Integrated into Selenium-Jupiter framework
      CONS OF SELENIUM
      • 8
        Flaky tests
      • 4
        Slow as needs to make browser (even with no gui)
      • 2
        Update browser drivers

      related Selenium posts

      Kamil Kowalski
      Lead Architect at Fresha · | 28 upvotes · 4M views

      When you think about test automation, it’s crucial to make it everyone’s responsibility (not just QA Engineers'). We started with Selenium and Java, but with our platform revolving around Ruby, Elixir and JavaScript, QA Engineers were left alone to automate tests. Cypress was the answer, as we could switch to JS and simply involve more people from day one. There's a downside too, as it meant testing on Chrome only, but that was "good enough" for us + if really needed we can always cover some specific cases in a different way.

      See more
      Benjamin Poon
      QA Manager - Engineering at HBC Digital · | 8 upvotes · 2.2M views

      For our digital QA organization to support a complex hybrid monolith/microservice architecture, our team took on the lofty goal of building out a commonized UI test automation framework. One of the primary requisites included a technical minimalist threshold such that an engineer or analyst with fundamental knowledge of JavaScript could automate their tests with greater ease. Just to list a few: - Nightwatchjs - Selenium - Cucumber - GitHub - Go.CD - Docker - ExpressJS - React - PostgreSQL

      With this structure, we're able to combine the automation efforts of each team member into a centralized repository while also providing new relevant metrics to business owners.

      See more
      qTest Management logo

      qTest Management

      20
      37
      0
      A test management tool used for Project Management, Bug Tracking, and Test Management
      20
      37
      + 1
      0
      PROS OF QTEST MANAGEMENT
        Be the first to leave a pro
        CONS OF QTEST MANAGEMENT
          Be the first to leave a con

          related qTest Management posts

          Cucumber logo

          Cucumber

          973
          923
          36
          Simple, human collaboration.
          973
          923
          + 1
          36
          PROS OF CUCUMBER
          • 20
            Simple Syntax
          • 8
            Simple usage
          • 5
            Huge community
          • 3
            Nice report
          CONS OF CUCUMBER
            Be the first to leave a con

            related Cucumber posts

            Benjamin Poon
            QA Manager - Engineering at HBC Digital · | 8 upvotes · 2.2M views

            For our digital QA organization to support a complex hybrid monolith/microservice architecture, our team took on the lofty goal of building out a commonized UI test automation framework. One of the primary requisites included a technical minimalist threshold such that an engineer or analyst with fundamental knowledge of JavaScript could automate their tests with greater ease. Just to list a few: - Nightwatchjs - Selenium - Cucumber - GitHub - Go.CD - Docker - ExpressJS - React - PostgreSQL

            With this structure, we're able to combine the automation efforts of each team member into a centralized repository while also providing new relevant metrics to business owners.

            See more

            I am a QA heading to a new company where they all generally use Visual Studio Code, my experience is with IntelliJ IDEA and PyCharm. The language they use is JavaScript and so I will be writing my test framework in javaScript so the devs can more easily write tests without context switching.

            My 2 questions: Does VS Code have Cucumber Plugins allowing me to write behave tests? And more importantly, does VS Code have the same refactoring tools that IntelliJ IDEA has? I love that I have easy access to a range of tools that allow me to refactor and simplify my code, making code writing really easy.

            See more
            JavaScript logo

            JavaScript

            354.3K
            269.4K
            8.1K
            Lightweight, interpreted, object-oriented language with first-class functions
            354.3K
            269.4K
            + 1
            8.1K
            PROS OF JAVASCRIPT
            • 1.7K
              Can be used on frontend/backend
            • 1.5K
              It's everywhere
            • 1.2K
              Lots of great frameworks
            • 897
              Fast
            • 745
              Light weight
            • 425
              Flexible
            • 392
              You can't get a device today that doesn't run js
            • 286
              Non-blocking i/o
            • 237
              Ubiquitousness
            • 191
              Expressive
            • 55
              Extended functionality to web pages
            • 49
              Relatively easy language
            • 46
              Executed on the client side
            • 30
              Relatively fast to the end user
            • 25
              Pure Javascript
            • 21
              Functional programming
            • 15
              Async
            • 13
              Full-stack
            • 12
              Setup is easy
            • 12
              Future Language of The Web
            • 12
              Its everywhere
            • 11
              Because I love functions
            • 11
              JavaScript is the New PHP
            • 10
              Like it or not, JS is part of the web standard
            • 9
              Expansive community
            • 9
              Everyone use it
            • 9
              Can be used in backend, frontend and DB
            • 9
              Easy
            • 8
              Most Popular Language in the World
            • 8
              Powerful
            • 8
              Can be used both as frontend and backend as well
            • 8
              For the good parts
            • 8
              No need to use PHP
            • 8
              Easy to hire developers
            • 7
              Agile, packages simple to use
            • 7
              Love-hate relationship
            • 7
              Photoshop has 3 JS runtimes built in
            • 7
              Evolution of C
            • 7
              It's fun
            • 7
              Hard not to use
            • 7
              Versitile
            • 7
              Its fun and fast
            • 7
              Nice
            • 7
              Popularized Class-Less Architecture & Lambdas
            • 7
              Supports lambdas and closures
            • 6
              It let's me use Babel & Typescript
            • 6
              Can be used on frontend/backend/Mobile/create PRO Ui
            • 6
              1.6K Can be used on frontend/backend
            • 6
              Client side JS uses the visitors CPU to save Server Res
            • 6
              Easy to make something
            • 5
              Clojurescript
            • 5
              Promise relationship
            • 5
              Stockholm Syndrome
            • 5
              Function expressions are useful for callbacks
            • 5
              Scope manipulation
            • 5
              Everywhere
            • 5
              Client processing
            • 5
              What to add
            • 4
              Because it is so simple and lightweight
            • 4
              Only Programming language on browser
            • 1
              Test
            • 1
              Hard to learn
            • 1
              Test2
            • 1
              Not the best
            • 1
              Easy to understand
            • 1
              Subskill #4
            • 1
              Easy to learn
            • 0
              Hard 彤
            CONS OF JAVASCRIPT
            • 22
              A constant moving target, too much churn
            • 20
              Horribly inconsistent
            • 15
              Javascript is the New PHP
            • 9
              No ability to monitor memory utilitization
            • 8
              Shows Zero output in case of ANY error
            • 7
              Thinks strange results are better than errors
            • 6
              Can be ugly
            • 3
              No GitHub
            • 2
              Slow
            • 0
              HORRIBLE DOCUMENTS, faulty code, repo has bugs

            related JavaScript posts

            Zach Holman

            Oof. I have truly hated JavaScript for a long time. Like, for over twenty years now. Like, since the Clinton administration. It's always been a nightmare to deal with all of the aspects of that silly language.

            But wowza, things have changed. Tooling is just way, way better. I'm primarily web-oriented, and using React and Apollo together the past few years really opened my eyes to building rich apps. And I deeply apologize for using the phrase rich apps; I don't think I've ever said such Enterprisey words before.

            But yeah, things are different now. I still love Rails, and still use it for a lot of apps I build. But it's that silly rich apps phrase that's the problem. Users have way more comprehensive expectations than they did even five years ago, and the JS community does a good job at building tools and tech that tackle the problems of making heavy, complicated UI and frontend work.

            Obviously there's a lot of things happening here, so just saying "JavaScript isn't terrible" might encompass a huge amount of libraries and frameworks. But if you're like me, yeah, give things another shot- I'm somehow not hating on JavaScript anymore and... gulp... I kinda love it.

            See more
            Conor Myhrvold
            Tech Brand Mgr, Office of CTO at Uber · | 44 upvotes · 11.2M views

            How Uber developed the open source, end-to-end distributed tracing Jaeger , now a CNCF project:

            Distributed tracing is quickly becoming a must-have component in the tools that organizations use to monitor their complex, microservice-based architectures. At Uber, our open source distributed tracing system Jaeger saw large-scale internal adoption throughout 2016, integrated into hundreds of microservices and now recording thousands of traces every second.

            Here is the story of how we got here, from investigating off-the-shelf solutions like Zipkin, to why we switched from pull to push architecture, and how distributed tracing will continue to evolve:

            https://eng.uber.com/distributed-tracing/

            (GitHub Pages : https://www.jaegertracing.io/, GitHub: https://github.com/jaegertracing/jaeger)

            Bindings/Operator: Python Java Node.js Go C++ Kubernetes JavaScript OpenShift C# Apache Spark

            See more
            Git logo

            Git

            293.4K
            175.7K
            6.6K
            Fast, scalable, distributed revision control system
            293.4K
            175.7K
            + 1
            6.6K
            PROS OF GIT
            • 1.4K
              Distributed version control system
            • 1.1K
              Efficient branching and merging
            • 959
              Fast
            • 845
              Open source
            • 726
              Better than svn
            • 368
              Great command-line application
            • 306
              Simple
            • 291
              Free
            • 232
              Easy to use
            • 222
              Does not require server
            • 27
              Distributed
            • 22
              Small & Fast
            • 18
              Feature based workflow
            • 15
              Staging Area
            • 13
              Most wide-spread VSC
            • 11
              Role-based codelines
            • 11
              Disposable Experimentation
            • 7
              Frictionless Context Switching
            • 6
              Data Assurance
            • 5
              Efficient
            • 4
              Just awesome
            • 3
              Github integration
            • 3
              Easy branching and merging
            • 2
              Compatible
            • 2
              Flexible
            • 2
              Possible to lose history and commits
            • 1
              Rebase supported natively; reflog; access to plumbing
            • 1
              Light
            • 1
              Team Integration
            • 1
              Fast, scalable, distributed revision control system
            • 1
              Easy
            • 1
              Flexible, easy, Safe, and fast
            • 1
              CLI is great, but the GUI tools are awesome
            • 1
              It's what you do
            • 0
              Phinx
            CONS OF GIT
            • 16
              Hard to learn
            • 11
              Inconsistent command line interface
            • 9
              Easy to lose uncommitted work
            • 7
              Worst documentation ever possibly made
            • 5
              Awful merge handling
            • 3
              Unexistent preventive security flows
            • 3
              Rebase hell
            • 2
              When --force is disabled, cannot rebase
            • 2
              Ironically even die-hard supporters screw up badly
            • 1
              Doesn't scale for big data

            related Git posts

            Simon Reymann
            Senior Fullstack Developer at QUANTUSflow Software GmbH · | 30 upvotes · 9.9M views

            Our whole DevOps stack consists of the following tools:

            • GitHub (incl. GitHub Pages/Markdown for Documentation, GettingStarted and HowTo's) for collaborative review and code management tool
            • Respectively Git as revision control system
            • SourceTree as Git GUI
            • Visual Studio Code as IDE
            • CircleCI for continuous integration (automatize development process)
            • Prettier / TSLint / ESLint as code linter
            • SonarQube as quality gate
            • Docker as container management (incl. Docker Compose for multi-container application management)
            • VirtualBox for operating system simulation tests
            • Kubernetes as cluster management for docker containers
            • Heroku for deploying in test environments
            • nginx as web server (preferably used as facade server in production environment)
            • SSLMate (using OpenSSL) for certificate management
            • Amazon EC2 (incl. Amazon S3) for deploying in stage (production-like) and production environments
            • PostgreSQL as preferred database system
            • Redis as preferred in-memory database/store (great for caching)

            The main reason we have chosen Kubernetes over Docker Swarm is related to the following artifacts:

            • Key features: Easy and flexible installation, Clear dashboard, Great scaling operations, Monitoring is an integral part, Great load balancing concepts, Monitors the condition and ensures compensation in the event of failure.
            • Applications: An application can be deployed using a combination of pods, deployments, and services (or micro-services).
            • Functionality: Kubernetes as a complex installation and setup process, but it not as limited as Docker Swarm.
            • Monitoring: It supports multiple versions of logging and monitoring when the services are deployed within the cluster (Elasticsearch/Kibana (ELK), Heapster/Grafana, Sysdig cloud integration).
            • Scalability: All-in-one framework for distributed systems.
            • Other Benefits: Kubernetes is backed by the Cloud Native Computing Foundation (CNCF), huge community among container orchestration tools, it is an open source and modular tool that works with any OS.
            See more
            Tymoteusz Paul
            Devops guy at X20X Development LTD · | 23 upvotes · 8.9M views

            Often enough I have to explain my way of going about setting up a CI/CD pipeline with multiple deployment platforms. Since I am a bit tired of yapping the same every single time, I've decided to write it up and share with the world this way, and send people to read it instead ;). I will explain it on "live-example" of how the Rome got built, basing that current methodology exists only of readme.md and wishes of good luck (as it usually is ;)).

            It always starts with an app, whatever it may be and reading the readmes available while Vagrant and VirtualBox is installing and updating. Following that is the first hurdle to go over - convert all the instruction/scripts into Ansible playbook(s), and only stopping when doing a clear vagrant up or vagrant reload we will have a fully working environment. As our Vagrant environment is now functional, it's time to break it! This is the moment to look for how things can be done better (too rigid/too lose versioning? Sloppy environment setup?) and replace them with the right way to do stuff, one that won't bite us in the backside. This is the point, and the best opportunity, to upcycle the existing way of doing dev environment to produce a proper, production-grade product.

            I should probably digress here for a moment and explain why. I firmly believe that the way you deploy production is the same way you should deploy develop, shy of few debugging-friendly setting. This way you avoid the discrepancy between how production work vs how development works, which almost always causes major pains in the back of the neck, and with use of proper tools should mean no more work for the developers. That's why we start with Vagrant as developer boxes should be as easy as vagrant up, but the meat of our product lies in Ansible which will do meat of the work and can be applied to almost anything: AWS, bare metal, docker, LXC, in open net, behind vpn - you name it.

            We must also give proper consideration to monitoring and logging hoovering at this point. My generic answer here is to grab Elasticsearch, Kibana, and Logstash. While for different use cases there may be better solutions, this one is well battle-tested, performs reasonably and is very easy to scale both vertically (within some limits) and horizontally. Logstash rules are easy to write and are well supported in maintenance through Ansible, which as I've mentioned earlier, are at the very core of things, and creating triggers/reports and alerts based on Elastic and Kibana is generally a breeze, including some quite complex aggregations.

            If we are happy with the state of the Ansible it's time to move on and put all those roles and playbooks to work. Namely, we need something to manage our CI/CD pipelines. For me, the choice is obvious: TeamCity. It's modern, robust and unlike most of the light-weight alternatives, it's transparent. What I mean by that is that it doesn't tell you how to do things, doesn't limit your ways to deploy, or test, or package for that matter. Instead, it provides a developer-friendly and rich playground for your pipelines. You can do most the same with Jenkins, but it has a quite dated look and feel to it, while also missing some key functionality that must be brought in via plugins (like quality REST API which comes built-in with TeamCity). It also comes with all the common-handy plugins like Slack or Apache Maven integration.

            The exact flow between CI and CD varies too greatly from one application to another to describe, so I will outline a few rules that guide me in it: 1. Make build steps as small as possible. This way when something breaks, we know exactly where, without needing to dig and root around. 2. All security credentials besides development environment must be sources from individual Vault instances. Keys to those containers should exist only on the CI/CD box and accessible by a few people (the less the better). This is pretty self-explanatory, as anything besides dev may contain sensitive data and, at times, be public-facing. Because of that appropriate security must be present. TeamCity shines in this department with excellent secrets-management. 3. Every part of the build chain shall consume and produce artifacts. If it creates nothing, it likely shouldn't be its own build. This way if any issue shows up with any environment or version, all developer has to do it is grab appropriate artifacts to reproduce the issue locally. 4. Deployment builds should be directly tied to specific Git branches/tags. This enables much easier tracking of what caused an issue, including automated identifying and tagging the author (nothing like automated regression testing!).

            Speaking of deployments, I generally try to keep it simple but also with a close eye on the wallet. Because of that, I am more than happy with AWS or another cloud provider, but also constantly peeking at the loads and do we get the value of what we are paying for. Often enough the pattern of use is not constantly erratic, but rather has a firm baseline which could be migrated away from the cloud and into bare metal boxes. That is another part where this approach strongly triumphs over the common Docker and CircleCI setup, where you are very much tied in to use cloud providers and getting out is expensive. Here to embrace bare-metal hosting all you need is a help of some container-based self-hosting software, my personal preference is with Proxmox and LXC. Following that all you must write are ansible scripts to manage hardware of Proxmox, similar way as you do for Amazon EC2 (ansible supports both greatly) and you are good to go. One does not exclude another, quite the opposite, as they can live in great synergy and cut your costs dramatically (the heavier your base load, the bigger the savings) while providing production-grade resiliency.

            See more