Skip to content

General

General

Categories

580 results found

  1. Like I want quarter wise data or team-wise data I have to create a report for that instead of that if you can give that functionality in the dashboard that will be very helpful.

    4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. In integration with Jira, any story created in jira has to be explicitly imported to PT. You can give user an option to enable real-time integration with JIra, which means, when a new user story in created in Jira, it is automatically imported to PT in requirements module.

    4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. Current ly Excution Progress chart only support fillter of project with less than 10 000 instance (total instance of whole project).

    4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. The past two QA jobs I've had required us to fill in our actual results even if they matched the expected results. Currently they want us to fill it in with something simple to show that we acknowledged it passing as expected, for regulatory purposes.

    Could we get some type of configuration for this so that if we pass or pass all and leave the fields blank they will be filled in with custom text (e.g.: "Passed as expected")?

    4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. When a filter name is low on the page and you click on the menu icon next to it, it scrolls you to the top, causing you to have to scroll back down the page to the filter.

    4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. 4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. 4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. BDD automation has a feature call "Scenario Outline", where you can define a table data for the test. This feature is based in step parameters.
    PractiTest hosts also a step parameters feature, although the table data is defined at run time, unlike BDD automation, which is defined at test definition time
    This can be solved with a custom field hosting the table data, where automation framework can retrieve it using the API, but the problem is when we try to create a run.
    I have tried FireCracker with a Scenario Outline test and the report is not accurate because it…

    4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. It would help if users could convert Scripted Tests into Exploratory. We only started using Exploratory tests in the past year so if we could convert Scripted tests into exploratory that would help.

    4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. When doing a batch Edit I would like to be able to link the requirement in the edit functionality. That will help streamline the process of tracing backwards and forwards, making managing these projects easier!

    4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. Need flexibility to reuse of existing filters instead of creating multiple duplicate filters at different levels

    4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. Currently, there is an option only to sort them in ascending order. If you need to sort them in reverse order, you can only do it manually

    4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. Expand traceability in Requiremnets to include Linked Requirements., This will enable association between Business Requirements to Functional Requirements etc.

    Also supports a heirachy of requirements (drill down).

    It appears that the change would be relatively simple given the existing Traceability functions in Requirements for Linked Tests and Linked Issues. Just add Linked Requirements.

    4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. 4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. When I import tests with steps, just like I can "call" the test between the steps in existing Test, or one I'm creating manually, I'd like to have an option like that in Import spreadsheet.
    For example, another Step column "Called Test ID" where I can put the ID of a test and it will be called.

    4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. Add ability to define a step as a non-critical step, and thus a failure on this step would not fail the test.

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. (1) link test cases to externally stored requirements (In fogbugz) and push the externally stored requirement data into Practitest requirements for reporting/dashboard.
    (2) Add a Push link next to the Defects field in the Test Run Result screen which pushes a bug report to the external system (FogBugz) without leaving Practitest and make a copy in 'Issues' at the same time for reporting/dashboard.
    (3) Hyperlinks to externally held data if only linking to issues/requirements in the external system and not pushing data to and fro (hovering the mouse cursor over a fogbugz case ID in either issues or requirements screen…

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. When using the Redmine 2-way integration, currently users need to go back to Redmine in order to see the bug list or in order to edit the bugs.

    It would be very helpful if Practitest users would be able to view and edit the bugs from the "Issues" tab or even view them on the different dashboard widgets.

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. By making Step Expected Results a Pass/Fail checklist so a user can check off the results as they go.

    It would also be nice if these Expected Results are stored in a library for use in future test steps as well.

    This increases test accuracy and allows for a more efficient management of expected results. Also, in the event of a bug, you can automatically report exactly which expected result was not met.

    This will greatly reduce time and energy spent by the development team trying to figure out exactly what failed to occur.

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  20. This could be done by integrating with requirements tools directly or by integrating for instance by using Jira use cases & requirements (ideally integration with Jira should be used when Jira is then also integrated with a requirements tool like Jama).
    This will help traceability and reporting on requirements through the whole development and QA process

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
1 2 6 8 10 28 29
  • Don't see your idea?