CSV\XML\RSS Feeds are QAed

In Content centric organizations, feeds are one of the core part that needs to update every time when

1. New Contents are Uploaded.
   
2. 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 > < & ) which may break XML \ RSS Feeds.

• 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 redirects user to the subscription services.
They are paychecks for companies.

2. Validate Content Details are not broken.
Content Details are like Content Descriptions on which user read and subscribe service or purchase content from company like Content Name, Type, Usage , Marketing Phases.

3. Validate each correct Content has its own correct Content details.
Content details are mapped correctly with each other.

Validating above tasks MANUALLY is not a practical way as we all know in middle to big scale organization we would have more then 10,000+ contents in QA. There are some automation ways to validate above task more effectively and efficiently -- I will focus light on them in my next post .

NUnit basics for new bees

In smaller to bigger project, here are some basics about how to automate Unit testing with NUnit framework on .Net Platform.

Where NUnit spot on SDLC?
In other words, we can ask when to start unit automation on project? It depends on various parameters say for example Complexity of Method(s) / API(s) or Classes in production cycle - How Method(s) API(s) / Classes are called by other Method(s) / API(s) / Classes in production cycle.

We can start NUnit automation after completion of any independent Method / API / its Class created at production and making automation continued towards parallel of development cycle of more dependent Method(s) / API(s) / Classe(s).

Say for example we have small class library project in C#.

Now lets start NUnit Automation in 7 simple steps :

1. Create New Test C# Project (Here Named TestProject) and add production class (.dll) reference.
2. Add reference NUnit.Frameworkto the TestProject.
3. Add attribute "TestFixture" to mark as Test Class and so NUnit GUI can recognize.
4. To create Test Category / Test-Cases group, add attribute “Category” passing with CategoryName as a param say for here [Category(“TestCategory1”)].
5. Add attribute “Test”to the test-cases which will teardown inside test-class.
6. To implement test-case , create Object of the AUT Class and call Assert with its various methods as required.
7. Save the project and Open this on NUnit GUI and last run the test.

   

Njoy, Nimesh - (Get more NUnit stuff on http://www.nunit.org )