Azure Storage Client Tools

Introduction

If you want to view/interact with your azure storage data you'll need to have an Azure Storage client tool.
You can either user Microsoft tools or third party tools.

Microsoft Tools

Azure Storage Client Tool	Tables	Queues	Files	Free	Web	Windows	OSX	Linux
Microsoft Azure Portal	X	X	X	Y	X
Microsoft Azure Storage Explorer	X	X	X	Y		X	X	X
Microsoft Visual Studio Server Explorer
Third-party Tools
Azure Storage Client Tool	Tables	Queues	Files	Free	Web	Windows	OSX	Linux
Cloud Portam	X	X	X	Trial	X
Cerabrata: Azure Management Studio	X	X	X	Trial		X
Cerabrata: Azure Explorer			X	Y		X
Azure Storage Explorer	X	X		Y		X
CloudBerry Explorer			X	Y/N		X
Cloud Combine	X	X		Trial		X
ClumsyLeaf: AzureXplorer, CloudXplorer, TableXplorer	X	X	X	Y		X
Gladinet Cloud				Trial		X

Happy testing and... make it green, becomes a dream :).

Selenium - Uploading file when input is invisible

Do you have problems simulating file upload in case the input is invisible?

You can make the element visible by using javascript in your code. Make the element visible and then call SendKeys to enter the path into the upload file input.

Happy testing and... make it green, becomes a dream :).

Protractor - Analyze Browser Console Logs with protractor-screenshoter-plugin

Have you ever wondered if there is any possibility to capture browser errors when you run protractor tests? 
There is. One solution is to use protractor-screenshoter-plugin that works for jasmine2.
After the entire .spec run, a folder e2e will be generated that will include an index.html. Open it and you will get your browser logs.

This plugin has 2 reporting parts:
- screenshot parts
- console reports
The first one will take screenshots for each jasmine2 expect success/failure, run time, failure reason, and what is important, the browser's logs.

The second one is an overview for all browser console logs.

How to install

Usage

Happy testing and... make it green, becomes a dream :).

ISTQB Agile Tester Exam Impressions

What is ISTQB Agile Tester

If you are working in an Agile project you may be interested in taking ISTQB Agile Tester exam.

This a certification that appeared in June 2014, so it's quite new and I wasn't able to find too many documents, sample questions, exam impressions about it.

As described on ISTQB site, Agile Tester is an extension of the foundation level. An 'extension' is a training and a certification module that is focused on a specific topic, such as domain-specific testing practices, specific testing techniques, specific testing methods.

The interest in Agile Tester certification is the following:

What are the objectives of istqb Agile Tester Syllabus?

Preparing for the Exam

The study materials that I used for this certification are:

- ISTQB documents

• Syllabus
• Sample exam questions
• Glossary of terms

- Books

• Agile Testing: A Practical Guide for Testers and Agile Teams, a book that is very useful not only to prepare for the exam but to gain more knowledge about Agile, in general

- Sample Exam questions that you can find on the internet. I gathered a list of URLs that contains sample questions, for some of them you need to pay.

• ASTQB sample exam questions
• Amazon sample questions1
• Amazon sample questions2
• other links

1. http://www.testingexcellence.com/istqb-quiz/istqb-agile-tester-certification-exam-sample-test/
2. http://www.ebay.com/itm/ISTQB-Foundation-Level-Agile-Tester-Full-Length-Online-Practice-Test-/221781994210
3. http://www.proprofs.com/quiz-school/story.php?title=istqb-agile-ext-quiz-chapter-1
4. http://www.gocertify.com/astqb-and-istqb/istqb-practice-quiz-agile-tester-ctfl-at-quiz-1
5. http://www.gocertify.com/astqb-and-istqb/istqb-practice-quiz-agile-tester-ctfl-at-quiz-2
6. https://testpot.com/exams/istqb-online-test/56b3dac62527e42823ff53bf/

Exam Tips

• You need to read the syllabus for at least 5 times. Some K1 parts should be memorized (e.g. agile values, agile principles, xp values, etc.).
• Focus on the Learning objective. While you read the question try to be aware to what chapter that question belongs and remember what is the learning objective for that chapter. Try to be aware of the distribution of questions per chapter (see below). For example question 14, belongs to chapter 2.1 and you'll need to know the difference between testing activities in agile and in traditional projects, question 26 belongs to 3.1 and you should know what is TDD, BDD and ATD.
• There will be 26 questions. Questions 13, 25 and 40 are K1, from Glossary of Terms.

• Even question of K2 and K3 may require strong knowledge of the syllabus
• I remember that there are 2 questions from 1.1.1, 1.1.2, 1.1.3 and 1.2.3, 3.1.3, 3.3.2
• The majority of K3 questions are practical, e.g. what are the valid acceptance test cases for a user story, asses quality risks, perform exploratory testing
• Take care with the exam time cause is flying, especially when K3 questions start (from question number 29).

Good luck!

Happy testing and... make it green, becomes a dream :).

Postman - Embed 'Run in Postman' button in Visual Studio Online

Today we managed to embed Postman button in Visual Studio Online dashboard.

Why should we embed this? The Run button in Postman opens a collection of API endpoints directly in the user’s Postman app. By embedding this in your documentation, you'll be able to link a collection of endpoints and workflows that help developers onboard onto your API faster.

What should we do to have this?

First of all, you need to include a new widget type in Visual Studio Online.

You must have permissions to add new widgets.

Then, you need to add a new dashboard tile:

The next steps are to install a widget from Extension Gallery.

Visual Studio Online administrator will need to approve your request. Once this is approved you'll be able to see the new widget in the available list.

Next, you need to obtain embedded code from Postman. Follow these steps:

1. Click on the collection you would like to embed and hit Share

2. Shift to the Embed Button tab

3. Click in Generate Code. This will upload the collection to Postman servers

4. Select an environment, if you want to export it

5. Hit Copy to Clipboard

Now, you need to include this embedded code into your Visual Studio Online widget. Add a new widget of type IFrame Dashboard Widget. Copy the text in Url field, choose a title and a dimension and, what is most important, before the copied text add this data:text/html,<html><body>, at the end add this </body></html>. You have the freedom to customize the widget as you wish. All you have to do is to write html code. There is only one limitation: Url field should not exceed 4000 characters.

When you'll press Run in Postman button, you'll need to right click on Postman for Chrome + open in a new tab, and after this, Postman app. will be opened and will import the collection and/or environment automatically. One observation: the environment will be duplicated every time you'll import it. So, make sure to delete the old one if you already performed an import.

Use Chrome to follow these steps.

That's it. 

Happy testing and... make it green, becomes a dream :).

Protractor Test Run Results - Jasmine2-html-reporter

One way to see protractor test run results, is to use an existing package, called jasmine2-html-reporter that will help you see a reporter in html format for Jasmine and Protractor. The big advantage of this is that it's able to generate a screenshot every time a test test fails.

In order to use it you need to npm install it and to add it in your protractor config.js file, in onprepare function

$ npm install protractor-jasmine2-html-reporter

var Jasmine2HtmlReporter = require('protractor-jasmine2-html-reporter');

exports.config = {
   // ...
   onPrepare: function() {
      jasmine.getEnv().addReporter(
        new Jasmine2HtmlReporter({
          savePath: './protractor/reports/logs/htmlReports',

          takeScreenshots: true,
          takeScreenshotsOnlyOnFailures: true
        })
      );
   }
}

There are other options that you can use, like FixedScreenshotName, CleanDestination, showPassed, etc.

The test results will show
- 'passed' for every 'expect' inside a spec ('it' statement)
- if there is no 'expect' inside 'it', it will be marked with 'skipped'
- if an error occurs, it will show an error + a screenshot

Later, you can use test results files in a CI system, like Jenkins and attach the screenshots for failed tests as artifacts.

Happy testing and... make it green, becomes a dream :).

Protractor - Show test run time in your logs

In this short article we will see how can we show the test run duration in a log file, displayed in hours, minutes, seconds.

There are some moments when we can add data in a log file: 
- jasmine started, meaning that we will add info in a log file when we started to run tests
- suite started; inside a .spec file we can have different suites (describe); we can add logs for each describe
- spec started; inside a suite we can have multiple specifications (it); we can add logs for each it
- spec done
- suite done
- jasmine done

To add the elapsed time, we need to capture start time in jasmine started and end time in jasmine done.

Happy testing and... make it green, becomes a dream :).