In Content centric organizations, feeds are one of the core part that needs to update every time when New Contents are Uploaded. New Categories \ Groups are introduced for Old Contents. As we know first one is very repetitive task -- so need repetitive validation. Second one is less repetitive but much costlier and involve high risk – so need more rigorous validation as well. Both missions have some kind of common problems : Feed Generator Software\Content System retrieve Content Data ( URL(s) \ Content Details ) which may have ASCII Characters and Memory Garbage and old inactive URL(s)– URL(s) where contents are not actually accessible by user. Feed may contain non compatible XML data( like special characters > Feed may not have broken content URL(s) and Content Details but they may be mapped wrongly. It means Content Details for one Content may not present its own Content URL or in opposite. So for QA, we expect to 1. Validate Broken Content URL(s) Content URL(s) are usually...