We are going to implement an Agile process soon, and think BDD would be a good fit to reduce misunderstandings between the teams.
I would like to get more information about how PractiTest can be used for BDD, both for manual and automated testing, and understand the setup and requirements for implementing BDD, so we can be prepared when we decide to adopt it as part of our Agile process.
Great question! Sounds like you’re planning this the smart way 
BDD can really help close the gaps between product, dev, and QA, and PractiTest makes it pretty easy to manage that process once you get going.
For manual BDD, you can create BDD-style tests right in the Test Library using “Given / When / Then.” Each line becomes a test step you can mark as pass or fail during a run. It’s super handy for making sure everyone understands what the behavior should be, and you still get all the good PractiTest stuff like traceability, dashboards, and reports.
For automation, PractiTest integrates nicely with tools like Cucumber, SpecFlow, or Behave using FireCracker. It uploads your feature files and test results automatically, so your BDD scenarios show up alongside manual tests in the same project — one place for everything.
Before rolling out BDD, we recommend:
Training your team on writing clear Gherkin scenarios (moving forward, SmartFox AI will be able to help with that, too, BTW)
Starting small (one feature or team) to refine your process.
Creating custom fields and defining conventions so your manual and automated scenarios stay in sync.
Setting up your PractiTest project structure and dashboards for visibility.
Once everything’s in place, you’ll have a smooth, transparent Agile process where everyone speaks the same testing language.
You can learn more about BDD setup and automation in PractiTest here: BDD Testing Overview and FireCracker for BDD.