Posts

Typical Project flow with QA Loop in Jira (Atlassian)

Image
Last week, one of my friend needs some help to establish Project\QA workflows on Jira (Atlassian) So here I am happy to share some of my odd solution. Project Flow problems or hard to implement in Jira were * One stage splits with multiple stages in flow. * More than one stages merges to one stage. Here We have Brainstorming splits to UT - ST stage and Dev Review - QA Review merges with Review stage executed by System Group Members in project flow. One issue splits with more than one issues, can also be implemented with sub-tasks feature but it may not push next stage in the project flow as the project progresses; all sub-tasks are linked to the parent task only, may not execute inline flow; may not give more control to administrator\lead and may be more complicated to maintain. Sub-tasks may not be merged to one task on transitions after Dev. Review / QA Review merges to Review stage. Core objective is to implement flow that anyone can see each stage of the flow and can

Combinations n Permutations in QA

Combinations n Permutations are very useful in software testing. It help to find possible test-data / testcases. This session will provide details about 1. Some basics about Combinations 2. Logic to find possible combinations for taking k numbers of items from n number items at a time. 1. Some basics about Combinations. You might be come across with below example in old school days. We have set { "ant", "bug", "cat", "dog", "pig" } and If we want to take 3 elements at a time then we would have possible combinations as { "ant", "bug", "cat" } { "ant", "bug", "dog" } { "ant", "bug", "pig" } { "ant", "cat", "dog" } { "ant", "cat", "pig" } { "ant", "dog", "pig" } { "bug", "cat", "dog" } { "bug", "cat", "pig&qu

Automate QA Feeds task [continuous to last post]

Image
Continuous post of CSV\XML\RSS Feeds are QAed To validate Feed URL(s) are not broken ; we can use XML DOM. Below is script that validates broken link. To validate ASCII Character , I have used below script. You can create excel custom tool where you centralize all feeds , verifies broken resources before creating actual feed.

CSV\XML\RSS Feeds are QAed

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 > < & ) 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 Br

NUnit basics for new bees

Image
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 : Create New Test C# Project (Here Named TestProject) and add production class (.dll) reference. Add reference NUnit.Frameworkto the TestProject. Add attribute "TestFixture" to mark as Test C