<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Burp on James Jardine</title><link>https://jamesgaryjardine.com/tags/burp/</link><description>Recent content in Burp on James Jardine</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Wed, 10 Sep 2014 13:57:09 +0000</lastBuildDate><atom:link href="https://jamesgaryjardine.com/tags/burp/index.xml" rel="self" type="application/rss+xml"/><item><title>QA and Security Pt. 2: Software Testers</title><link>https://jamesgaryjardine.com/qa-and-security-pt-2-software-testers/</link><pubDate>Wed, 10 Sep 2014 13:57:09 +0000</pubDate><guid>https://jamesgaryjardine.com/qa-and-security-pt-2-software-testers/</guid><description>&lt;p&gt;Lets start by discussing the type of QA that tests software to ensure it is working as designed. These are the bug finders of the QA world. The process starts by a developer creating some functional code and then deploying it to an environment specific to the QA team. The QA team then uses its knowledge of how the application is supposed to function and determines if it is performing properly. Any bugs identified get filed and sent back for remediation (hopefully).&lt;/p&gt;</description></item></channel></rss>