560 results found

1. Integrate steps parameters with FireCracker (and/or API)

   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 does not match the parameter in the report with the parameter in the test.
   So, the new feature for PractiTest would be integrate steps parameters with FireCracker in order to go back to step definition and get its steps parameters and parse the step name in the report to act accordingly.

   Example:
   Test Library. Test. Steps
   Given an "anonymous" api consume
   When he asks for "{{page}}" page of "users"
   Then he gets a "SYNCHRONOUS_OK" response
   And the number of items per page matches response meta info
   And users response fields are populated

   Automation framework xml report file
   <testsuite name="As an anonymous api consumer I can get any page of users.As an anonymous api consumer I can get any page of users" tests="2" errors="0" failures="0" skipped="0" time="0.000933" timestamp="2021-01-27T13:05:22.684581" hostname="MacBook-Pro-13-Ton.local"><testcase classname="As an anonymous api consumer I can get any page of users.As an anonymous api consumer I can get any page of users" name="As an anonymous api consumer I can get any page of users. InstanceId=34428562 -- @1.1 " status="passed" time="0.000477"><system-out>
   <![CDATA[
   @scenario.begin
   Scenario Outline: As an anonymous api consumer I can get any page of users. InstanceId=34428562 -- @1.1
   Given an "anonymous" api consumer ... passed in 0.000s
   When he asks for "intermediate" page of "users" ... passed in 0.000s
   Then he gets a "SYNCHRONOUS_OK" response ... passed in 0.000s
   And the number of items per page matches response meta info ... passed in 0.000s
   And users response fields are populated ... passed in 0.000s

   @scenario.end

   ]]>
   </system-out></testcase><testcase classname="As an anonymous api consumer I can get any page of users.As an anonymous api consumer I can get any page of users" name="As an anonymous api consumer I can get any page of users. InstanceId=34428562 -- @1.2 " status="passed" time="0.000457"><system-out>
   <![CDATA[
   @scenario.begin
   Scenario Outline: As an anonymous api consumer I can get any page of users. InstanceId=34428562 -- @1.2
   Given an "anonymous" api consumer ... passed in 0.000s
   When he asks for "last" page of "users" ... passed in 0.000s
   Then he gets a "SYNCHRONOUS_OK" response ... passed in 0.000s
   And the number of items per page matches response meta info ... passed in 0.000s
   And users response fields are populated ... passed in 0.000s

   @scenario.end

   ]]>

   FireCracker should

   1.- Check
   When he asks for "last" page of "users" ... passed in 0.000s
   And
   When he asks for "{{page}}" page of "users"

   1. Get that "page" step parameter got "last" value

   2. Check
      When he asks for "intermediate" page of "users" ... passed in 0.000s
      And
      When he asks for "{{page}}" page of "users"

   3. Get that "page" step parameter got "intermediate" value

   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… more

   4 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

2. Add Ability to Convert Scripted Test into Exploratory

   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 Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

3. Link Requirements via Batch Edit

   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 Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   1 comment  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

4. Need flexibility to reuse of existing filters instead of creating multiple duplicate filters at different levels

   Need flexibility to reuse of existing filters instead of creating multiple duplicate filters at different levels

   4 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

5. Allow to sort list field values in descending order

   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 Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

6. Linked Requirements in Requirements Traceability

   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 Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

7. In Instance reports, keep the order of instances the way they're sorted in the instance view of each test set
   4 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   1 comment  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

8. When importing tests, enable the option to use "Call to Test" to existing tests

   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 Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

9. Non-critical Step

   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 Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   under review  ·  0 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

10. Improve Fogbugz Integration (Push data to and from Pracitest)

    (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 should open preview details about the external (fogbugz) case and clicking it should take me to the external link. Test metrics/dashboard for externally held data will be required (eg: requirements covered/completed/passed/failed, issues raised/closed etc)
    (4) Please enable indexing for the external reference numbers so that they are searchable (ie: I can search by external reference number which for me means Fogbugz Case number)

    (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… more

    3 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    waiting for supporters  ·  0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

11. Add date-based and "show most recent only" filter options to "Instance" report types.

    It would be very helpful to have a report shat shows only the most recently run test instance and exclude the older test instances for the applicable filter.

    3 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

12. Field data set on 1 screen and showing back on other screens

    For example:
    I have 1 Custom field browser (list) that have some values in it (Chrome, Firefox Safari etc.)
    I set that custom field on the screen:
    - Test
    - Instance
    - Issue

    When I Create new Test and I set the Browser: Firefox when im done with the Test --> Il Create TestSet & Instance = When im in the instance screen I see the Custom field Browser thats already filled in with 'Firefox' that I have selected in the screen Test.

    Start the instance and there is a Issue --> Create an Issue, Open the Issue screen and there is the custom field Browser also thats already filled in with 'Firefox'

    Value of the custom field Browser thats connected with the Test. comes back in the Instance & Issue screens. And have selected 1 time.

    That was my Idea. But its not only for list, i was also thinkg for number fields.

    For example:
    I have 1 Custom field browser (list) that have some values in it (Chrome, Firefox Safari etc.)
    I set that custom field on the screen:
    - Test
    - Instance
    - Issue

    When I Create new Test and I set the Browser: Firefox when im done with the Test --> Il Create TestSet & Instance = When im in the instance screen I see the Custom field Browser thats already filled in with 'Firefox' that I have selected in the screen Test.

    Start the instance and there is a Issue --> Create an Issue, Open the Issue screen and… more

    3 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating
    Ido Tandy responded

    
    

13. Better test step UI for running and editing test cases

    Step result - Rather than just change the colour of the step name/heading, which gets lost in the links and other text above/below it, shade whole the step area/row.

    If step N has a result provided (pass, fail, block), and all the steps between step 0 and step N are blank, set steps ) to N all to Pass. This will reduce the number of clicks a tester has to do in order to work through running a test case.

    Allow a step to be flagged as "needing review" while the test is being run so it can be completed without a failure. This suggests the step may or may not be correct. In reports, mark any test with steps needing review with a flag icon.

    Allow Save and Run after editing test case steps and creating a test case.

    When editing test cases, the 3 blank fields aren't descriptive. A small label under each, default text that is replaced but never saved, or something more obvious indicating what each field is for would be easier to follow for people coming to the product for the first time.

    Step result - Rather than just change the colour of the step name/heading, which gets lost in the links and other text above/below it, shade whole the step area/row.

    If step N has a result provided (pass, fail, block), and all the steps between step 0 and step N are blank, set steps ) to N all to Pass. This will reduce the number of clicks a tester has to do in order to work through running a test case.

    Allow a step to be flagged as "needing review" while the test is being run so it can be completed… more

    3 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    started  ·  0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

14. Implement ways to manage the automation job queue

    Currently, there is no way to see what jobs (test runs) have been started or are in the queue to run. Furthermore, there is no way to cancel a job once it has started. Also, only entire test sets can be sent to the job queue, when there are many times when it would be beneficial to submit only a subset of tests in the test set. For example, when you want to re-run a failed test, there is currently no way to do that without executing the entire test set again.

    3 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

15. Add to the Report a simple metrics of the overall test progress

    To display the percentage of the total number of tests that have been executed (test marked as, Passed, Failed, Not Complete)

    i.e. 6 total tests, 2 marked as Not Complete, 1 passed and 3 No Run.

    Percentage Test Executed = 50%

    Along with metrics to capture the Test completed status (Passed Test Vs Total number of tests) as a percentage.

    i.e. 6 total tests, 2 marked as Not Complete, 2 passed and 2 No Run.

    Percentage Test Completed: 33%

    3 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

16. Allow field 'Actuel result' inside steps to be mandatory

    Some results of a step are so important you need to be sure the tester have described the result. By do it possible to make this field mandatory you can manage this situation.

    3 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

17. Option to add text in Dashboard

    It would be useful to have some kind of text summary next to graph in Dashboard:

    Example: "this and that test was failed because issue-x (minor), but the build is still released."

    Could you please add this feature to the Dashboard?

    -Ossi

    3 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating
    Ido Tandy responded

    
    

18. Add ability to set called test parameters from the parent (or calling) script

    The "Call steps from another test" feature works well for testing a matrix of parameter values. However it doesn't allow for passing in static, never changing values to called tests for the sole purpose of re-usable script steps and provide a single point of change (aka single point of maintenance).

    For example:
    * You have an portal based site which has several "apps" or sub-sites.
    * When a user logs into the portal the get presented with a dashboard page with links to each of apps.

    Ideally the tester would be able to create a single login script that can be called from other scripts passing in the UID, PWD, and destination app. The parent or "calling" script in this case would always use the same destination, and may or may not use the same credentials.

    Another example:
    * You have a process that can be completed once successfully, but if you attempt it a second time the user should be thwarted and an error message should be displayed.

    In this case the ideal approach for the tester would be to call the same script with the repetitive steps twice specifying a different desired outcome for each called instance.

    Even better would be for the called script, which may have numerous parameters, be able to be used with this parent script as well as others. In this case the tester would want to be able to statically set some if not all of these parameters depending on the intent of the parent test.

    These situations do not need to, nor should, have the parameter values set at a Test Instance level since they are not relative to the parent test being run various ways or using different data sets etc. The parent test has a static purpose, but the tester wants to enjoy script step re-use and have a single point of change when the site is changed.

    The "Call steps from another test" feature works well for testing a matrix of parameter values. However it doesn't allow for passing in static, never changing values to called tests for the sole purpose of re-usable script steps and provide a single point of change (aka single point of maintenance).

    For example:
    * You have an portal based site which has several "apps" or sub-sites.
    * When a user logs into the portal the get presented with a dashboard page with links to each of apps.

    Ideally the tester would be able to create a single login script that can… more

    3 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

19. add ability to drag and drop to tests

    the user should have an ability to drag and drop his tests inside a filter in case he wants to arrange his tests in a prioritized order

    3 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

20. Add the ability to search all the tests that has "call to test" of a specific test
    3 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating
    Ido Tandy responded