Skip to main content

Security Testing Sessions Meet - 17th June - Video Recordings

Hello Everyone,

In the first session on 'Security Testing', we had a discussion about following topics:

1. Web Security Testing
2. HTTP Protocol
3. Session ID & Cookies
4. OWASP
5. Live HTTP Header (Firefox Addon)

We covered the basics of Web technology and discussed about how the web technology works as such. In the subsequent session, we shall concentrate on specific threats.



Some of the attendees requested me to provide the url details of OWASP Top 10 document and other tools. I have provided them below for your reference:

1. OWASP Top 10 document
2. OWASP WebScarab
3. OWASP ZAP Proxy
4. OWASP Testing Guide

You can find the video link of the session here.

Please let me know if you require any further details.

Thanks,
V.Vasanth

Comments

  1. Hi,

    Thanks for sharing!

    Does the video have audio also? I can't hear any speech, but volume should be ok.

    Have a great week!


    Best regards,
    Jari

    ReplyDelete
  2. The sound is ok for me for the video shared above.

    ReplyDelete
  3. Hi Jari,

    Video contains Audio as well. Please check your speakers...

    ReplyDelete
  4. Not able to listen to Audio, tried it on multiple machines.

    ReplyDelete

Post a Comment

No spam only genuine comments :)

Popular posts from this blog

Where is my defect ID?

Don't you feel ecstatic when your automated tests find bug? After all tests finding bugs give us a sense of accomplishment, is not it? And this is followed by usual cycle of defect reporting, retesting and hopefully closure of defect. But at times defects are deferred to next or future releases. Which causes test method to fail for subsequent releases. And if you are dealing with a test suite having 100s of tests then it may become difficult to remember if there was a defect reported for a failing test? How do you deal with such situation. How about adding defect-id to @description tag of TestNG test. Hence it is reported on automated test report and we would know if defect exists for a failing test - How do you track defect-id of a failing test?

Return only first or last element from webelements collection

We often come across situation when there are multiple elements on a page and we probably like to exercise only a few of them using selenium webdriver. May be just first and last element. For example on a search result page we may like to click on only first and last link and not all. This is when Iterables API comes handy. (By the way I am assuming that you have already completed watching selenium training videos :)). Once we have collection of web element then we can use Iterables to get only first or last element as following - Consider that we fetch collection of element as - List< WebElement > webElements = getDriver().findElements(By. id ( "htmlID" ));   Now we can get the first web element from this collection as -  WebElement firstElement = Iterables. getFirst (webElements,  getDriver().findElement(By. id ( "defaultElement" )));   Herein second argument -   (getDriver().findElement(By. id ( "defaultElement" )))    in the me

Selenium Tutorial: Pattern Mathing using Selenium

I must confess I have never been admirer of Regular Expression but then there are times you can not escape from it, especially while working on a website which has dynamic contents appeared in static text and you want to validate it. like - "Validate that this text appears and there is 123 here and 456 here" And the test condition is 123 and 456 could be any three digits but number if digits should not be more than three. In a crude way we can at least test this - Assert.assertTrue(selenium.getText("elementLocator").contains("Validate that this text appears and there is")); but what if text goes wrong after "and there is"... what if more than 3 digits appear in text. This is where pattern matching/regular expression comes for our rescue and we can use matches method of String class to achieve same. So the assertion would be - String text = selenium.getText("elementLocator"); Assert.assertTrue(text.matches("Validate