Wednesday, April 25, 2012

"""

Question on your mind - Is the title """?
Answer from me - Yes, its 3 double quotes


This -> """ (3 double quotes) made me happy as I'm the first person to inform to my office colleagues about it. I came to know this because of my laziness & Google.

Hey guys, I can feel that you guys are losing your patience. Without any stretches, I will spot-on about this matter.

""" - Its multi-line comments used in Cucumber (Might been used in many places but no idea from my end).

For multi-line comments, most of my friends were using '#' (hash tag) for each & every line. I just wanted to make multi-line comments and got the answer and informed to all.



::Example::
Feature: my feature
""" some block comment
still block comment
""" end of block comment

Scenario: my feature
""" some block comment
still block comment
""" end of block comment


[courtesy: http://stackoverflow.com]


Nature, Cucumber, Capybara & etc...

It’s been 2 days (not complete 16 hours) for me >> Started learning Cucumber. Just asked questions to most of them in my company related all the ridiculous statements & words I came through (used in Ruby/Rails/Cucumber). Yes, this is interesting.

Just started Features, Scenarios, Given, When, And, Then. As it was so difficult for me to start the basic level from installations itself, thought of posting a post regarding what are these from my understanding.

Feature - It’s used for some test scenario crowd description.
Scenario - It precedes the test name. It’s similar to Test case name.
Given - The instruction after this keyword is some prerequisite or set of connections.
When – The instruction after this keyword is some action to be made during the test.
Then - Typically precedes the instructions responsible for a range of validations
And - And is used for concatenating purpose.

Will post the basic commands in another post & thanks for the interest invoked in me related to Cucumber.



Monday, April 16, 2012

Open Quality Testing

:: OQT ::


<< Open Quality Testing >>



Wednesday, April 4, 2012

On Running Crucial Test Data

Blank: See if suitable “error messages” are shown.
Example: ‘’ [i.e., empty.] To avoid this blank error message, we can also provide suggestion as to disable the Submit/any conditional Button. [Example: Login button can be in disabled state until some data is been provided in both Email ID & Password field.]

Valid: Valid input data is properly saved in database. [Data needs to be displayed as per the client requirements.]
Example: (i) For Name field, valid data is “Snacky” & not “159203”.
(ii) For Tax impound, valid data can be “-14,000”, if that is what the client request is.


Invalid: On providing the Negative values & alphanumeric string inputs, you can check for invalid test data. [It depends on that particular field.]
Example: (i) For Name field, invalid data is “159203” & not “Snacky”.
(ii) For Tax impound, invalid data can be “14,000”, if client requires for ‘-ve values’ alone.


Range: Data set which is out of range data. Identify application boundary cases and prepare data set that will cover lower as well as upper boundary conditions.
Example:
In an organization: Recruitment Rules are;
0–15 >> Don’t hire
16–17 >> Can hire on a part-time basis only
18–54 >> Can hire as full-time employees
55–99 >> Don't hire

- What about ages -3 and 101? , this is what range data is all about.

Bulky: This data set should be large in volume.
Example: 60 MB file

Illegal: Make one data set of illegal data format (one set might have symbols). System should not accept illegal data format. ‘Error messages’ should be generated according to the data.
Example: It depends on the file, which you prepare with regards to the data format.