I have a QA Jenkins Job and I am trying to set Cronjob in QA Jenkins Job. So whenever the cronjob triggers the QA jenkins job, it need to take lastsuccessfulbuild artifact of Dev Jenkins Job. Is there any way we could achieve this?

I have this code

<div class="text-right rankings-list-volume">1200.50</div>

I have to get 1200.50 text. How can I do this?

I'm trying automate an Angular application. The only drawback I have at the moment is that I don't want to use Protractor, I want to automate using Selenium/Eclipse. I have tried it but the problem is that locator keeps changing whenever I rerun the test. I have browsed through the net and found no concrete solution to this. Snippet of one field in the websites:

<input _ngcontent-wle-c93="" formcontrolname="FirstName" mattooltip="Enter First Name" maxlength="50" matinput="" placeholder="First Name" class="mat-input-element mat-form-field-autofill-control ng-tns-c47-3 ng-pristine ng-invalid ng-touched" cdk-describedby-host="" id="mat-input-0" aria-invalid="true" aria-required="false" aria-describedby="mat-error-0">

id="mat-input-0" keeps changing

It's hard to suggest something without seeing what you've got and what's being criticized.

Just a tiny idea on how to make your test-cases more general: try to make use of some kind of repositories.
These can be UserRepository (having GoodUser, BadUser; GoodUser.Admin, GoodUser.Customer, etc).
Such strategies are applied in automation testing.

This way, instead of having

1. Enter "Login1" into 'login field';
2. Enter "Password1" into 'password field';
3. Press 'Sign in' button...

You'll simply have

1. Sign in as GoodUser.Customer;

And if you have some other field added to the login process later, you won't bother editing dozens of test-cases.

Good luck!

You might consider using a test coverage tool that isn't tied to the infrastructure in the way Emma is. This avoids the problems with incompatabilities with said infrastructure.

Our Java Test Coverage tool instruments your source code, making it independent of the compiler and runtime system. You compile your code and execute/test it however your like (system tests, unit tests, manual interaction), and it collects test coverage data in a Java array in a TestCoverage class, as the tests run. At the end of execution (you define that, although exit from main is a common definition), that test coverage data is written somehow to a file, eventually to be displayed by the test coverage tool. While the Java Test Coverage tool provides a default class implementation that writes the array to a disk file using Java file primitives, you can easily override the implementation with any code you like, and store the array in any place where it can be eventually retrieved by another mechanism to be turned into a file, and then displayed.

This will work with your manual exercising of code.

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?

Do you know if there is a way to return to previous state or somehow restore the tests that I already run before deleting. Our testing is manual and Test Cases are linked to Product Backlog Items.

Manual QA, more commonly known as Blackbox QA, is far from dead.

It's true that unit tests and general automated tests can cover at least 90% of code-path testing. What many don't realize is that the last manual 10% can be the some of the most important work a software and hardware organization can do.

Let's take the user interface, for example. A unit test can tell you that a check box is placed in the right location, and turns on and off as expected. What the test can't tell you is that it's horribly bitmapped and looks terrible with the hideous purple and yellow color scheme in the application.

The most important reason for Blackbox QA is that you end up with strong customer advocate inside your organization. Many of these QA people (myself included), have more of a creative background than a programming background. While some may think of this as a failing, these are the people who don't care about how the code works - they care about how the product works. They spend time thinking like a customer, rather than a developer; "Oh, my almost dead iPod is finished syncing, that means I can close my laptop and just let it charge. Yup, and then I'll just pull it out when my machine is asleep (even though I was playing music from it on my computer) and everything will be fine."

Developers and testers know how a product is supposed to work, and all exercise a product to specification. It's a good tester's job to use the product in a careless way, to make sure that bad stuff doesn't happen. Yank a USB drive from a computer while you're copying data, are you crazy?!? Sure, that's a really stupid idea. But people do it all the time. And a good QA person will do just that, to make sure that pulling a hard drive doesn't take a whole system down. Or turning off WiFi when downloading a movie, or syncing music while purchasing new content and then changing your account password and email address at the same time. Or installing an OS on an MP3 player and trying to boot from it, then pulling the player from the system while it's booted from the device (Yup, I did that, and found a really good bug from it).

I have a QA Jenkins Job and I am trying to set Cronjob in QA Jenkins Job. So whenever the cronjob triggers the QA jenkins job, it need to take lastsuccessfulbuild artifact of Dev Jenkins Job. Is there any way we could achieve this?