There are various of security tools. If I were you I'd download system called BackTrack - www.backtrack-linux.org which has plenty of them. You can test almost everything, including sociotechnics, security of application, security of server, security of network etc. every kind of "security" has its own tools. There is one good software that tests website against security called SET more on http://www.backtrack-linux.org/backtrack/social-engineering-toolkit-training/

If you want test WEB sites you should check this video http://vimeo.com/21631598

There are plenty of tools to scan websites you will get them when you download the system I've given you link above.

There is one more powerful tool to use -> http://www.metasploit.com/ you can read more about it on this site.

Hope I've helped

In the DEV job you need to archive the artifacts you want to transfer (post build operation -> archive artifacts).

In the QA job you need to Copy Artifacts from a different job, select your DEV job name, and select latest successful.

I am using pytest for automation. I have so many test cases and have one test cases as skipped test like below,

def test_step(index, description):
"""
    Logs the start of a test step.
"""
    # code for print log

Now, when any my test file executed and the report is generated, this test_step is also consider as a skipped test case in the report.

How can i remove skipped test cases from html report??

You conduct usability testing:

• To find problems in complex processes
• To collect unbiased user opinions
• To get insights that improve the overall user experience

1. Test together

2. You can use another database, but completely authentic (and who prevents you from making a full backup of everything before testing, and saving in a couple of copies, as a reference - in the case of yours?)

3. Everything needs to be done, as close as possible to production - if changing the folder is not critical, then you can.

4. Test a small block of the entire testing spectrum (some data) in both modes and see the difference - if they are not essential, then on dev it is quite possible. Of course, for the purity of the experiment, there is always a puddle of production - but look at the expediency and take the necessary parameters.

In general, the closer you are to production, the better, you need to move away from this only in unavoidable cases. The results of such a test can not only serve as an argument, but also protect the developer - in case something comes out after, if suddenly - everything happens in life, but after such a test (production) it is impossible to foresee everything, and of course, it is difficult to suspect the development in which something manipulation.

If it's a page form, Submit button should be on the left side:

But if you have a modal form, the button should be on the right side of the form: