What will be the test case for the condition:
On some criteria i.e 'resolution still not taken' ,the user with this criteria is blocked to visibility of an issue information?
Test case can be like this:
Steps:
1) Open the application.
Expected result: Application should get opened successfully.
2) Open the issue resolution status module.
Expected Result: Issue resolution status module should get opened successfully.
3) Check the status of issue.
Expected Result:
If status of issue is 'resolution still not taken' then user with this criteria is blocked to visibility of this issue.
If status is something else then do whatever your application says to do.
Note: I just mentioned raw structure of test case. You can write this in format which you use for your test case.
Related
I have the xUnitFileImport scheduled job configured in my polarion project (as described in Polarion documentation) to import e2e test results (formatted to JUnit test results)
<job cronExpression="0 0/5 * * * ? *" id="xUnitFileImport" name="Import e2e Tests Results" scope="system">
<path>D:\myProject\data\import-test-results\e2e-gitlab</path>
<project>myProject</project>
<userAccountVaultKey>myKey</userAccountVaultKey>
<maxCreatedDefects>10</maxCreatedDefects>
<maxCreatedDefectsPercent>5</maxCreatedDefectsPercent>
<templateTestRunId>xUnit Build Test</templateTestRunId>
<idRegex>(.*).xml</idRegex>
<groupIdRegex>(.*)_.*.xml</groupIdRegex>
</job>
This works and I get my test results imported into a new test run and new test cases are created. But if I run the import job multiple times (for each test run) it creates duplicate test case work items even though they have the same name, which leads to this situation:
Is there some way to tell the import job to reference the existing testcases to the
newly created test run, instead of creating new ones?
What i have done so far:
yes I checked that the "custom field for test case id" in the "testing > configuration" is configured
yes I checked that the field value is really set in the created test case
The current value in this field is e.g. ".Login" as i don't want the classnames in the report.
YES I still get the same behaviour with the classname set
In the scheduler I have changed the job parameter for the group id because it wasn't filled. New value is: <groupIdRegex>e2e-results-(.*).xml</groupIdRegex>
I checked that no other custom fields are interfering, only the standard fields are set
I checked that no readonly fields are present
I do use a template for the testcases as supported by the xUnitFileImport. The testcases are successfully created and i don't see anything that would interfere
However I do have a hyperlink set in the template (I'll try removing this soon™)
I changed the test run template from "xUnit Build test" to "xUnit Manual Test Upload" this however did not lead to any visible change
I changed the template status from draft to active. Had no change in behaviour.
I tripple checked all the fields in the created test cases. They are literally the same, which leads to the conclusion that no fields in the testcases interfere with referencing to them
After all this time i have invested now, researching on my own and asking on different forums, I am ready to call this a polarion bug unless someone proves me this functionality is working.
I believe you have to set a custom field that identifies the testcase with the xUnit file you're importing, for the importer to identify the testcase.
Try adding a custom field to the TestCase workitem and selecting it here.
Custom Field for Test Case ID option in settings
If you're planning on creating test cases beforehand, note that the ID is formatted form the {classname}.{name} for a given case.
If I have the cypress code:
cy.get('[testid="cancel-button"]').should('not.exist')
cy.get('[testid="reset-button"]').should('not.exist')
cy.get('[testid="other-button"]').should('not.exist')
of course in cypress open I can see the cy.get(XXX) criteria (in my case, the testid attribute) in the log, but for cypress run the HTML log only outputs:
Expected <button.bp3-button> not to exist in the DOM, but it was continuously found.
How is this helpful at all? I will have no way of knowing which one failed because all I see is <button.bp3-button>. I want to see the testid attribute in the cy.get() call. Is there any way to get the cy.get(XXX) criteria to be where <button.bp3-button> is in the failure log?
After executing our test automation we are sending the results into Rally. Here are the steps that we are following:
Create new Test Set
Add Test Case to Test set - The test case
already exists in a test folder
Query for the test case within the test set - We added this additional read since we were receiving concurrency issues trying to immediately post results after adding the test case to the testset
Post the results to the testcase within the testset.
The issue we are running into is in step 3 above. Sometimes, when a read is done to find the test case in the test set, it is unable to find it and so the results cannot be posted.
We have actually adjusted the code so it attempts 4 times with a 20 second delay between the third and 4th attempt and there are still several where results cannot be posted to Rally.
If anyone else has run into this issue and could provide guidance on a resolution that would be great
I am using clj-webdriver to fill out a form in my test case.
(quick-fill-submit {"#firstname" "Firstnam"}
{"#lastname" "Lastnaem"}
{"#username" "Username"}
{"#password" "Password"}
{"#password2" "Password"}
{"#roles" "user"})
(click "button#add-user")
Every time I run this code in my test case the third value is filled in blank.
I moved the fields around and verified it. It is always the third field.
When execute my test case step by step in a repl it works fine but when
running it through lein test it fails.
This seems to be some kind of timing issue. When I for example stall the
execution by adding a
(wait-until #(= 1 2) 10000)
between the two functions the field gets filled. A simple
(Thread/sleep n)
does not work in this case. Why is Selenium not filling in the form correctly?
WebDriver and AJAX calls usually require tweaking the wait settings. You should try setting implicit-wait to something bigger than 0 (which is the default). Another option would be to use wait-until and a predicate that checks for the presence of the elements.
I am using Selenium IDE to record some scenarios and wanted to check if a particular text is present on the page. I inserted a command "VerifyTextPresent". However, it always returns the result as true even when the particular text is not present.
What can be the probable reason? Do I need to modify anything?
Looking at the sourcecode it looks like you are putting the text you are searching for in the incorrect field.
verifyTextPresent (and assert...) has only two parameters unlike verifyText which also requires a target.
Unlike verifyText the text element you are searching for should be entered into the second field 'Target' not in 'Value'.
thus the code becomes
<tr>
<td>verifyTextPresent</td>
<td>XYZ</td>
<td></td></tr>
I made the same mistake when learning Selenium as the field names are misleading!
Selenium assertions have different modes:
All Selenium Assertions can be used in
3 modes: "assert", "verify", and
"waitFor". For example, you can
"assertText", "verifyText" and
"waitForText". When an "assert" fails,
the test is aborted. When a "verify"
fails, the test will continue
execution, logging the failure.
Try assertTextPresent. This should abort the test immediately.
check that page : http://release.seleniumhq.org/selenium-remote-control/1.0-beta-2/doc/java/com/thoughtworks/selenium/SeleneseTestBase.html#assertTrue%28boolean%29
assert and verify text fields build boolean results with using resource code.