XSpecs helps you collaboratively write and maintain specs that reflect the state of your products and are synchronized across all your tools.
Fragmented specs create a disconnect between team members, which leads to bugs and delays. We created XSpecs to close this gap. It allows everyone in the software development lifecycle to organize, develop, test and manage specs. The result: seamless "hand-offs" and a more productive team that creates ever more value at higher speeds and at higher quality.
XSpecs gives a boost to every part of the software development lifecycle.
Product Owners
People that work with customers and stakeholders, and manage products and backlogs.
Product Owners
People that work with customers and stakeholders, and manage products and backlogs.
XSpecs allow you to communicate the business value and intended outcomes clearly and precisely, which reduces guesswork and leads to a smooth delivery cycle. This means you can build the product right the first time around through a shared understanding of what needs to be done.
Unlike acceptance criteria on tickets which are ephemeral, specs are long lived and act as a means for you to know what the system capabilities are today and in the future.
Designers
People that design user experiences, information architecture, wireframes, visual assets and the likes.
Designers
People that design user experiences, information architecture, wireframes, visual assets and the likes.
Collaboratively bring your designs to life by enriching storyboards, wire-frames and visual designs with behavioural specs. These allow you describe and communicate precisely how the experience and designs should behave and leaves nothing to chance.
Specs are also an incredible way to get feedback from the team on not only the visual aspects of designs but also the inner workings, which leads to less rework and higher quality.
Developers
People that write code, automated tests, infrastructure, and all the things that create digital products.
Developers
People that write code, automated tests, infrastructure, and all the things that create digital products.
Clear up any misunderstandings or imprecision about your work before you start coding. And when you discover new specs or changes to existing specs as you code, XSpecs will seamlessly expose any specs you write at development time to the rest of the team without you having to lift a finger.
This establishes a single source of truth that provides both specifications and documentation of your system for all to see and collaborate on in the near and long term.
QAs
People that look for issues at every level within the holistic product development lifecycle.
QAs
People that look for issues at every level within the holistic product development lifecycle.
XSpecs removes the need for test scripts altogether by using specs as the source of truth of what the system should and shouldn't do. You can find spec bugs before a single line of code is written, and improve the specs by posting bug reports as new specs or modifications to existing ones.
Work alongside your test automation suite by combining your test results. This is a powerful technique that allows you to kiss regression bugs goodbye and focus on exploratory testing.
XSpecs is a one-stop shop where product managers, designers, developers, QAs and anyone else can produce, consume and collaborate over specs. Specs can be written by different people in different tools, and they can be tested with both automation and manual testing.
Agile, Lean, Waterfall or whatever - XSpecs does not force any process or way of working. It enables collaboration over specs in a non-intrusive way, across your team, tools, process and technologies.
Ensure specs get reviewed by your whole team through powerful collaborative features like real-time editing, comments, mentions and resolutions.
Our easy-to-use editor allows anyone in the team to read and write specs, even specs that are deep in the codebase.
XSpecs magically integrates into the development lifecycle by translating your specs to and from Markdown, Gherkin, or TypeScript/ECMAscript files without you having to write a single line of code!
Planned support for:
Java / .Net / more
Collaboratively write specs on wiki pages, track them in your ticketing tool, store them in your code repositories, and report test results from any CI server like Circle, Travis, or Jenkins. Today we have deep integration with:
Coming soon:
Want to be part of the journey? Join the beta and have the chance to impact the product through your feedback.
Record your specs using the standalone XSpecs app, or in the tool of your choice and bring your team together to create a shared understanding of the task at hand. Socialize your specs, run workshops and continuously factor in feedback.
Put the *same* specs you wrote in step 1 on a ticket and prioritize on a Kanban board or schedule for sprint. If any late discoveries are made, you can make changes to the spec on that ticket and the changes will be reflected everywhere.
Use the *same* specs you wrote in previous steps and use as a the basis in your repository for writing automated tests. This helps developers write code that meets the specifications today, and to prevent future regression bugs from occurring.
XSpec provides an aggregated view of the current state of all specs and allows you to see humans and automation test results in one place. This powerful union provides full visibility and transparency into the entire system in a single glance.
Exploratory testing can be performed guided by the specs which creates focus by massively reducing the bug search space. XSpecs allows both manual QA and automated test results from continuous integration to be reported on specs.
Record your specs using the standalone XSpecs app, or in the tool of your choice and bring your team together to create a shared understanding of the task at hand. Socialize your specs, run workshops and continuously factor in feedback.
Put the *same* specs you wrote in step 1 on a ticket and prioritize on a Kanban board or schedule for sprint. If any late discoveries are made, you can make changes to the spec on that ticket and the changes will be reflected everywhere.
Use the *same* specs you wrote in previous steps and use as a the basis in your repository for writing automated tests. This helps developers write code that meets the specifications today, and to prevent future regression bugs from occurring.
Exploratory testing can be performed guided by the specs which creates focus by massively reducing the bug search space. XSpecs allows both manual QA and automated test results from continuous integration to be reported on specs.
XSpec provides an aggregated view of the current state of all specs and allows you to see humans and automation test results in one place. This powerful union provides full visibility and transparency into the entire system in a single glance.