Tuesday, October 29, 2013 #

Point to Taken Care while Microsoft SQL Patching Testing in Production

 

Point to Taken Care while Microsoft SQL Patching Testing in Production

It very critical testing like Paching testing

 

1. Build the Test Environment Parrel to Production Environment i.e Staging Environment

2 Check the Version of Application deployed is same as Production Environment if Staging Environment not parrel to production environment then risk of defect in production

3.Check End to End Flow of Appliction

4 Check the Eventlog entries

5 Check the performance of the Application .

 

Thanks & Regards

Abhishek

 

 

 

 

 

 

 

Posted On Tuesday, October 29, 2013 10:09 PM | Comments (0)

Friday, March 15, 2013 #

Microsoft Tool :Use Windows Live Writer for Blogs Writing

Use Windows Live Writer for writing blogs

URL to download :http://windows.microsoft.com/en-us/windows-live/essentials-other-programs

Great tools for offline writing and publish in blog site with Photos ,videos etc

Screen Capture when i open for my blog : http://geekswithblogs.net/AbhishekLohani/Default.aspx

windows live writer

 

Publish using windows live writer writer

will keep you posted when i will learn more interesting around it 

 Thanks & Regards

Abhishek Lohani

Posted On Friday, March 15, 2013 6:16 AM | Comments (0)

Thursday, March 14, 2013 #

Visual Studio Test Professional 2012 90-day trial

Hi All,

Visual Studio Test Professional 2012 is ideal for testers, business analysts, product managers, and other stakeholders who need team collaboration tools, but not a full development IDE. After installation, you can try Test Professional 2012 for up to 90 days.

Microsoft URL to download

http://www.microsoft.com/visualstudio/eng#downloadshttp://www.microsoft.com/visualstudio/eng#downloads

Thanks  To Microsoft for Excellent Product for Testing Profession :):)

 

Thanks & Regards

Abhishek Lohani

Posted On Thursday, March 14, 2013 3:23 AM | Comments (1)

Tips : Quality Centre :Copy and Paste Test suite from one Project to Another

1. Open the QC link in two separate browser windows

2 Select the Test suit

2.1 Edit – Copy from first browser

3 Edit -Paste as second browser.

4 select the option

Paste Test SetsfTest Set Folders to Target Project

If the test sets/test set folders contain related entities, you can:

€) Copy test sets/test set folders and link to existing related entities

Pastes the test sets/test set folders into the target project and links

them to existing related entities with the same name.

O Copy test sets/test set folders and related entities

Pastes the test sets/test set folders and related entities into the

target project. Related entities are renamed in the target project to

resolve any duplicate test names.

Q Copy test sets/folders without copying related entities

Pastes the test sets/folders into the target project without linking them

to any related entities.

OK Cancel Help

Paste Test SetsfTest Set Folders to Target Project

If the test sets/test set folders contain related entities, you can:

€) Copy test sets/test set folders and link to existing related entities

Pastes the test sets/test set folders into the target project and links

them to existing related entities with the same name.

O Copy test sets/test set folders and related entities

Pastes the test sets/test set folders and related entities into the

target project. Related entities are renamed in the target project to

resolve any duplicate test names.

Q Copy test sets/folders without copying related entities

Pastes the test sets/folders into the target project without linking them

to any related entities.

OK Cancel Help

5 click OK

Thanks & Regards

Abhishek Lohani

Posted On Thursday, March 14, 2013 2:02 AM | Comments (0)

Sunday, January 27, 2013 #

Why Requirement Traceability Matrix is important for any Software Development/ Maintenance project?

 

Requirement Traceability  matrix tells as the test coverage of test case before Going to Next phase of testing or before GO live of the software .

In Software Testing Life cycle  

·         First of all Requirement will be gather from the Business.

·         Second on the basis of requirements test case will be created 

·         Third Test case will be executed on build provided by developer

·         Fourth defect will be raised for failed test .

·         Fifth and Final go will be give when all test pass.  

But still how can we trust on tester / testing team that all requirements are covered?

A tester is a human being they will may be miss the requirement as Developer miss the requirement and tester tested the finished product and raised a defects.

Solution

To overcome the entire Problem we need Requirement Traceability matrix.

In Requirement Traceability matrix  

·         One Requirement will Map to N number of Test case

·         N number of Test case need to passed to covered that requirement  

Lots of Tool presents to maintain Requirement Traceability Matrix

1 HP - Quality Centre

2 VS2010- Microsoft Test Manager

3 Excel - (Manual Mapping) 

Thanks & Regards

Abhishek Lohani

Posted On Sunday, January 27, 2013 8:53 PM | Comments (4)

Wednesday, January 23, 2013 #

Biztalk Application Testing Life Cycle -Part 3

In BizTalk Application Testing Life Cycle -3 – Integration Testing

In BizTalk Application Testing Life Cycle -1 – we have tested the Application Functionality on the basis of Function requirement agreed with the business.

For Details Please Check:http://geekswithblogs.net/AbhishekLohani/archive/2012/09/19/biztalk-application-testing-life-cycle-part-1.aspxv

In BizTalk Application Testing Life Cycle -2 – we have tested the Application Functionality on the basis of Non Function requirement agreed with the business.

For Details Please Check:http://geekswithblogs.net/AbhishekLohani/archive/2013/01/22/biztalk-application-testing-life-cycle-part-2.aspxhttp://geekswithblogs.net/AbhishekLohani/archive/2013/01/22/biztalk-application-testing-life-cycle-part-2.aspx 

In BizTalk Application Testing Life Cycle -3 – we need to tested how the  Application/ System wiil interacting with Third Party software / Custom Software / Legacy sytem  as per agreed with business

Issue faced in Integration Testing

·         Might be the Input file schema changes during the development of system and valid file discarded by system

·         May be New Version / New release of Custom or Third Party Software is  release during new system development.

·         Requirement was fixed wrongly with assumption if this type of file will come following action will took place but not act when actual file came.

·         New Software support the legacy system to give the result end to end.

In BizTalk Application Testing Life Cycle -3 – Integration Testing

In BizTalk Application Testing Life Cycle -1 – we have tested the Application Functionality on the basis of Function requirement agreed with the business.

For Details Please Check:

In BizTalk Application Testing Life Cycle -2 – we have tested the Application Functionality on the basis of Non Function requirement agreed with the business.

For Details Please Check:

 

In BizTalk Application Testing Life Cycle -3 – we need to tested the Application with interacting with Third Party software  

Issue faced in Integration Testing

·         Might be the Input file schema changes during the development of system and valid file discarded by system

·         May be New Version / New release of Custom or Third Party Software is  release during new system development.

·         Requirement was fixed wrongly with assumption if this type of file will come following action will took place but not act when actual file came.

·         New Software support the legacy system to give the result end to end.

Thanks & Regards

Abhishek

Posted On Wednesday, January 23, 2013 7:56 PM | Comments (2)

Tuesday, January 22, 2013 #

Biztalk Application Testing Life Cycle Part 2

In Biztalk Application Testing Life Cycle Part 2 we cover Non Fuctional Testing

In Non Fuctional Testing we required test below areas as a part of Non Fuctional Testing

1 Acess Right - Filesahre, SQL, Biztalk etc

2 Security Testing - Password should be encrpted

3 Connectivity Testing - In Connectivity testing we test connectivities with the stubs or External System newly build system is intracting

4 Build Verification Test

5 Volume Test - How will the system will performan with Design volume , Peak Volume & More than Peak Volume

6 Operability Test

7 Alert Testing

8 Saok testing

Thanks

Abhishek

 

 

Posted On Tuesday, January 22, 2013 6:54 PM | Comments (0)

Wednesday, September 19, 2012 #

Biztalk Application Testing Life Cycle Part 1

The Function system i.e. System Testing

In the Functional System testing our approach is to test the Business Process rule i.e. functionality 

We test the system in following categories/ flow

                                                           

1 Positive Testing 

2 Negative testing 

We also need to check all the BP / Functional Requirement should be covered for that we need to use Quality Centre or VS2010 or Excel to maintain Traceability matrix.

Description

<!In Positive testing we covers all the positive flow testing scenarios such as 

1 Deployment Test 

2 Interface Flow Test - check the flow of interface without any error file processed successfully logged into event log 

3 All Functional Requirement testing scenarios such as

a) If x in the input file transform correctly in output file as z.

b) In CSV file having 10 records if 2 records are incorrect are properly rejected and correct records got processed correctly.

c) No message got suspended 

d) Check debating of file

e) Check ordering of file

f) Check Naming Convention of file

g) Check concurrency in the database

2. In negative testing we will cover how our system behaves when incorrect scenarios occurs such as

a)     Incorrect File name
b)     Incorrect data
c)      Incorrect file not validated with schema file
d)     Missing Mandatory fields
e)     Missing Optional fields
f)       Database unavailable
g)     In bound File share unavailable
h)     Outbout File share unavoidable

 

In Biztalk System Testing we test the Biztalk artifacts such as 

Map

Schema

Pipeline 

Adapter

. Net Component 


Note :

Unit test the code well before moving to System testing 

Code Coverage of unit test should be good i.e should be 80 - 90 %

Code Review should be done before giving the code / Sytem for System Testing


                         

 Thanks & Reagrds

Abhishek Lohani

 

Posted On Wednesday, September 19, 2012 10:06 PM | Comments (0)

Thursday, August 16, 2012 #

VS2010 Coded UI Test :Add or modify object properties Coded UI manually

 

Hi First of all know the defination of the object

Step  to be Performmed :-

 1 Edit with the code UI test builder and place the Cross hair control to know the defination of the Control

 2 Record the control and know the defination when you will know the object defination then add or modify the defination in UIMap.cs or UIMap.Designer.cs

Example how to implement above step

1.    I have Recorded the Login windows  control using vs2010 code ui test and pass the credentilas and add a Assert method and generate the Code . 

2.    From UIMap.Designer.cs copy the function in UIMap.cs and parametarized  the function with custom credentials using Resource file. and call the Function from the test .

Thanks

Abhishek kumar lohani

Note :- i have assumed person may know how to record the test using coded ui test in vs2010

 

Posted On Thursday, August 16, 2012 1:47 AM | Comments (0)

Saturday, August 11, 2012 #

Biztalk Application Testing Life Cycle

Biztalk  Application Testing Life Cycle

Content of Biztalk Application testing comprises

1 The Function system i.e System Testing

2 Non Function Testing i.e Performance Voulume Test

3 Integartion Testing

4 UAT

In current testing Scenario we follow both the V model and Agile Testing of Biztalk appliction

Both the Model are appropriate accoding to scenario

In Scenario 1 if business know what tpo develop with less changes in requirement then follow V model .

In Scenario 2 if business having changing requirement and will want to have some thing in running then go for Agile testing - Iteration wise or on the basis of sprit .

 

Thanks

Abhishek

 

Posted On Saturday, August 11, 2012 12:17 AM | Comments (1)

Copyright © AbhishekLohani

Design by Bartosz Brzezinski

Design by Phil Haack Based On A Design By Bartosz Brzezinski