Life as a QA Engg

10 Apr

“Product can’t be defined well until we tested, so developer be careful while coding

Day of a software tester starts by reading their emails & project updates.Testers also scan their mailbox for emails from their developers or Product owner giving them any update of the bugs that they had raised the previous day.After reading through the emails and project updates, tester would pick up the project assigned to them with the highest priority. Priority is decided generally by the discussion on daily scrum meetings.

Ideally, a daily scrum meeting is held in the morning, as it helps set the context for the coming day’s work.These scrum meetings are strictly time-boxed to 15-20 minutes.This keeps the discussion brisk but relevant.During the daily scrum, each team member answers the following three questions:

Wat was done yesterday?

Wat will be the plan today?

Are there any impediments in ur way?

If a newly implemented module is hitting UAT , then a Proper walk-Through session will be conducted by the concern product owner and developer.And based on the Session and Project Doc & Mock, tester will raise issues if it’s not met the expected goal.If the developer is not clear about the issue, he’ll be reassigned back to the tester with appropriate comments. It is, therefore, important for the tester to understand each note that the developer leaves on the ticket so that proper testing can be done.Occasionally, the bugs are small but if not fixed, they might have severe implications on the software.A software tester is required to report all types of bugs whether they’re important or unimportant. The difference, however, lies in the priority.

The basic model behind each company is to create products or services and sell them to customers for a profit. These products or services must live up to a certain quality standard expected by customers. If the quality level is not met, there are consequences to face for the business. Therefore, quality is important to a business for a number of reasons.So our feature testing team helps detect software glitches and bugs, which can be fixed before launching the software, and thus prevent getting a bad name for the startup. It is important for startups to launch detect-free products as it keeps the client happy and in the process, helps maintain a long-term relationship between the company and clients.

Software Testing Dictionary

24 Apr

Acceptance Testing: Testing conducted to enable a user/customer to determine whether to accept a software product. Normally performed to validate the software meets a set of agreed acceptance criteria.

Accessibility Testing: Verifying a product is accessible to the people having disabilities (deaf, blind, mentally disabled etc.).

Accuracy – Capability of software product or application to provide the agreed results or effectswith specified degree of precision.

Actual Result – Behavior produced or observed when a component or system is tested.

Ad Hoc Testing: A testing phase where the tester tries to break the system by randomly trying the system’s functionality. Can include negative testing as well. See also Monkey Testing.

Adaptability – is the capability of software product to be adapted for specified multiple environments without applying actions other than those provided for the specific purpose for the software considered.

Agile Testing: Testing practice for projects using agile methodologies, treating development as the customer of testing and emphasizing a test-first design paradigm. See also Test Driven Development.

Automated Software Quality (ASQ): The use of software tools, such as automated testing tools, to improve software quality.

Alpha Testing – Operational testing by intented users / customers or an independent test team at the developer’s location. Alpha testing is often employed for off the shelf software as a form of internal acceptance testing.

Analyzability- capability of the software product or system to be diagnosed for deficiencies or causes of failures in the software or for the parts to be modified to be identified.

Automated Testware – Testware used in test automation such as tool scripts etc.

Back to Back Testing – Software Testing in which more than one variants of a software system are executed with the same inputs and the outputs compared & analyzed in cases of discrepancies.

Basis Path Testing: A white box test case design technique that uses the algorithmic flow of the program to design tests.

Basis Set: The set of tests derived using basis path testing.

Beta Testing: Testing of a re-release of a software product conducted by customers.

Benchmark Test – A test that is be used to compare components or systems to each other or to a standard.

Big Bang Testing: Type of integration testing in which software elements and hardware
elements are combined all at once.

Binary Portability Testing: Testing an executable application for portability across system platforms and environments, usually for conformation to an ABI specification.

Black Box Testing: Testing based on an analysis of the specification of a piece of software without reference to its internal workings. The goal is to test how well the component conforms to the published requirements for the component.

Blocked test case – A test case which cannot be executed because the pre-conditions for its
execution are not fulfilled.

Bottom Up Testing: An approach to integration testing where the lowest level components are tested first, then used to facilitate the testing of higher level components. The process is repeated until the component at the top of the hierarchy is tested.

Boundary Testing: Test which focus on the boundary or limit conditions of the software being tested. (Some of these tests are stress tests).

Boundary Value – Input value or output value which is on the edge of an equivalence
partition or at the smallest incremental distance on either side of an edge. The example can be
minimum or maximum value of a range.

Boundary Value Coverage – %age of boundary values that have been exercised by a test suite.

Branch Coverage – %age of branches that have been exercised by a test suite. 100% branch coverage implies both 100% decision coverage and 100% statement coverage.

Bug: A fault in a program which causes the program to perform in an unintended or unanticipated manner.

Boundary Value Analysis: BVA is similar to Equivalence Partitioning but focuses on “corner cases” or values that are usually out of range as defined by the specification. his means that if a function expects all values in range of negative 100 to positive 1000, test inputs would include negative 101 and positive 1001.

Branch Testing: Testing in which all branches in the program source code are tested at least once.

Breadth Testing: A test suite that exercises the full functionality of a product but does not test features in detail.

Business Process Based Testing – An approach to software testing in which test cases are designed based on descriptions and knowledge of business processes and components.

CAST: Computer Aided Software Testing.

Capture/Replay Tool: A test tool that records test input as it is sent to the software under test. The input cases stored can then be used to reproduce the test at a later time. Most commonly applied to GUI test tools.

CMM: The Capability Maturity Model for Software (CMM or SW-CMM) is a model for judging the maturity of the software processes of an organization and for identifying the key practices that are required to increase the maturity of these processes.

Cause Effect Graph: A graphical representation of inputs and the associated outputs effects which can be used to design test cases.

Changeability – capability of the software or system to enable specified modifications to be implemented.

Classification Tree Method – Black box test design technique in which test cases, described by means of a classification tree which are designed to execute combinations of representatives of input and output domains.

Code Complete: Phase of development where functionality is implemented in entirety; bug fixes are all that are left. All functions found in the Functional Specifications have been implemented.

Code Coverage: An analysis method that determines which parts of the software have been executed (covered) by the test case suite and which parts have not been executed and therefore may require additional attention.

Code Inspection: A formal testing technique where the programmer reviews source code with a group who ask questions analyzing the program logic, analyzing the code with respect to a checklist of historically common programming errors, and analyzing its compliance with coding standards.

Code Walkthrough: A formal testing technique where source code is traced by a group with a small set of test cases, while the state of program variables is manually monitored, to analyze the programmer’s logic and assumptions.

Compatibility Testing: Testing whether software is compatible with other elements of a system with which it should operate, e.g. browsers, Operating Systems, or hardware.

Compliance – Capability of the software product to adhere to standards or regulations in laws and similar prescriptions.

Compliance Testing – Process of testing to determine the compliance of component or
system.

Component – minimal software item that can be tested in isolation.

Component Integration Testing – Software Testing performed to expose defects in the interfaces & interaction between components.

Compound Condition Testing – Testing tTwo or more single conditions joined by means of a logical operator.

Concurrency Testing: Multi-user testing geared towards determining the effects of accessing the same application code, module or database records. Identifies and measures the level of locking, deadlocking and use of single-threaded code and locking semaphores.

Conformance Testing: The process of testing that an implementation conforms to the specification on which it is based. Usually applied to testing conformance to a formal standard.

Context Driven Testing: The context-driven school of software testing is flavor of Agile Testing that advocates continuous and creative evaluation of testing opportunities in light of the potential information revealed and the value of that information to the organization right now.

Conversion Testing: Testing of programs or procedures used to convert data from existing systems for use in replacement systems.

Cyclomatic Complexity: A measure of the logical complexity of an algorithm, used in white-box testing.

Daily Build – It is a development activity where a complete system is compiled and linked every day so that a consistent system is available at any time including all latest changes.

Data Driven Testing: Testing in which the action of a test case is parameterized by externally defined data values, maintained as a file or spreadsheet. A common technique in Automated Testing.

Data Flow Testing – White box test design technique in which software test cases are designed to execute definition and use pairs of variables.

Database Integrity Testing: Testing the methods used to access and manage the data or database to ensure that during access to the database, data is not corrupted or unexpectedly deleted, updated or created.

Decision Condition Testing – White box test design technique in which test cases are designed to execute condition outcomes and decision outcomes.

Decision Table Testing – Black box test design techniques in which test cases are designed to execute the combinations of inputs put in a decision table.

Defect: Nonconformance to requirements or functional / program specification

Defect Management – Process of recognizing, investigating, taking action and disposing
of defects. It involves recording and tracking of defects by classifying them and identifying the impact.

Defect Masking – Occurrence in which one defect prevents the detection of another.

Dependency Testing: Examines an application’s requirements for pre-existing software, initial states and configuration in order to maintain proper functionality.

Depth Testing: A test that exercises a feature of a product in full detail.

Design Based Testing – Approach to test in which test cases are designed based on architecture and detailed design of the system.

Development Testing – A Formal or informal testing conducted by developers during the implementation of a component or system.

Documentation Testing – Testing of the quality of the documentation.

Dynamic Testing: Testing software through executing it. See also Static Testing.

Efficiency Testing – Process of testing to determine the efficiency of a software product.

Elementary Comparison Testing – Black box test design technique in which the concept of condition determination coverage is used to design the test cases are to execute combinations of inputs.

Endurance Testing: Checks for memory leaks or other problems that may occur with prolonged execution.

End-to-End testing: Testing a complete application environment in a situation that mimics real-world use, such as interacting with a database, using network communications, or interacting with other hardware, applications, or systems if appropriate.

Equivalence Class: A portion of a component’s input or output domains for which the component’s behavior is assumed to be the same from the component’s specification.

Equivalence Partitioning: A test case design technique for a component in which test cases are designed to execute representatives from equivalence classes.

Error Guessing – Test design technique where the experience of a tester is used to identify what defects might be present in the component or system under test.

Error seeding – Process of intentionally adding known defects to a component or system for the purpose of monitoring the rate of detection, removal and estimating the number of remaining defects.

Exhaustive Testing: Testing which covers all combinations of input values and preconditions for an element of the software under test.

Exploratory Testing: It is an informal test design technique where a tester actively controls the design of the tests as those tests are performed while testing to design new and better tests.

Functional Decomposition: A technique used during planning, analysis and design; creates a functional hierarchy for the software.

Functional Specification: A document that describes in detail the characteristics of the product with regard to its intended features.

Functional Testing:

· Testing the features and operational behavior of a product to ensure they correspond to its specifications.

· Testing that ignores the internal mechanism of a system or component and focuses solely on the outputs generated in response to selected inputs and execution conditions.

Frozen Test Basis – Test basis document that can only be modified or amended by a formal change control process.

Gorilla Testing: Testing one particular module,functionality heavily.

Gray Box Testing: A combination of Black Box and White Box testing methodologies: testing a piece of software against its specification but using some knowledge of its internal workings.

High Order Tests: Black-box tests conducted once the software has been integrated.

Independent Test Group (ITG): A group of people whose primary responsibility is software testing.

Inspection: A group review quality improvement process for written material. It consists of two aspects; product (document itself) improvement and process improvement (of both document production and inspection).

Integration Testing: Testing of combined parts of an application to determine if they function together correctly. Usually performed after unit and functional testing. This type of testing is especially relevant to client/server and distributed systems.

Installation Testing: Confirms that the application under test recovers from expected or unexpected events without loss of data or functionality. Events can include shortage of disk space, unexpected loss of communication, or power out conditions.

Localization Testing: This term refers to making software specifically designed for a specific locality.

Loop Testing: A white box testing technique that exercises program loops.

Monkey Testing: Testing a system or an Application on the fly, i.e just few tests here and there to ensure the system or an application does not crash out.

Negative Testing: Testing aimed at showing software does not work. Also known as “test to fail”.

Path Testing: Testing in which all paths in the program source code are tested at least once.

Penetration testing: Evaluating the security of a computer system or network by hacking. it is the process of actively evaluating your information security measures. For more datails, please see my other post on Penetration Testing

Performance Testing: Testing conducted to evaluate the compliance of a system or component with specified performance requirements. Often this is performed using an automated test tool to simulate large number of users.

Positive Testing: Testing aimed at showing software works. Also known as “test to pass”.

Quality Assurance: All those planned or systematic actions necessary to provide adequate confidence that a product or service is of the type and quality needed and expected by the customer.

Quality Audit: A systematic and independent examination to determine whether quality activities and related results comply with planned arrangements and whether these arrangements are implemented effectively and are suitable to achieve objectives.

Quality Circle: A group of individuals with related interests that meet at regular intervals to consider problems or other matters related to the quality of outputs of a process and to the correction of problems or to the improvement of quality.

Quality Control: The operational techniques and the activities used to fulfill and verify requirements of quality.

Ramp Testing: Continuously raising an input signal until the system breaks down.

Recovery Testing: Confirms that the program recovers from expected or unexpected events without loss of data or functionality. Events can include shortage of disk space, unexpected loss of communication, or power out conditions.

Regression Testing: Retesting a previously tested program following modification to ensure that faults have not been introduced or uncovered as a result of the changes made.

Release Candidate: A pre-release version, which contains the desired functionality of the final version, but which needs to be tested for bugs (which ideally should be removed before the final version is released).

Sanity Testing: Brief test of major functional elements of a piece of software to determine if its basically operational.

Scalability Testing: Performance testing focused on ensuring the application under test gracefully handles increases in work load.

Security Testing: Testing which confirms that the program can restrict access to authorized personnel and that the authorized personnel can access the functions available to their security level.

Smoke Testing: A quick-and-dirty test that the major functions of a piece of software work. Originated in the hardware testing practice of turning on a new piece of hardware for the first time and considering it a success if it does not catch on fire.

Soak Testing: Running a system at high load for a prolonged period of time. For example, running several times more transactions in an entire day (or night) than would be expected in a busy day, to identify and performance problems that appear after a large number of transactions have been executed.

Software Testing: A set of activities conducted with the intent of finding errors in software.

Static Analysis: Analysis of a program carried out without executing the program.

Static Analyzer: A tool that carries out static analysis.

Static Testing: Analysis of a program carried out without executing the program.

Storage Testing: Testing that verifies the program under test stores data files in the correct directories and that it reserves sufficient space to prevent unexpected termination resulting from lack of space. This is external storage as opposed to internal storage.

Stress Testing: Testing conducted to evaluate a system or component at or beyond the limits of its specified requirements to determine the load under which it fails and how. Often this is performance testing using a very high level of simulated load.

Structural Testing: Testing based on an analysis of internal workings and structure of a piece of software.

System Testing: Testing that attempts to discover defects that are properties of the entire system rather than of its individual components.

Testability: The degree to which a system or component facilitates the establishment of test criteria and the performance of tests to determine whether those criteria have been met.

Testing:

· The process of exercising software to verify that it satisfies specified requirements and to detect errors.

· The process of analyzing a software item to detect the differences between existing and required conditions (that is, bugs), and to evaluate the features of the software item (Ref. IEEE Std 829).

· The process of operating a system or component under specified conditions, observing or recording the results, and making an evaluation of some aspect of the system or component.

Test Bed: An execution environment configured for testing. May consist of specific hardware, OS, network topology, configuration of the product under test, other application or system software, etc. The Test Plan for a project should enumerated the test beds(s) to be used.

Test Case:

· Test Case is a commonly used term for a specific test. This is usually the smallest unit of testing. A Test Case will consist of information such as requirements testing, test steps, verification steps, prerequisites, outputs, test environment, etc.

· A set of inputs, execution preconditions, and expected outcomes developed for a particular objective, such as to exercise a particular program path or to verify compliance with a specific requirement.

Test Driven Development: Testing methodology associated with Agile Programming in which every chunk of code is covered by unit tests, which must all pass all the time, in an effort to eliminate unit-level and regression bugs during development. Practitioners of TDD write a lot of tests, i.e. an equal number of lines of test code to the size of the production code.

Test Driver: A program or test tool used to execute a tests. Also known as a Test Harness.

Test Environment: The hardware and software environment in which tests will be run, and any other software with which the software under test interacts when under test including stubs and test drivers.

Test First Design: Test-first design is one of the mandatory practices of Extreme Programming (XP).It requires that programmers do not write any production code until they have first written a unit test.

Test Harness: A program or test tool used to execute a tests.

Test Plan: A document describing the scope, approach, resources, and schedule of intended testing activities. It identifies test items, the features to be tested, the testing tasks, who will do each task, and any risks requiring contingency planning.

Test Procedure: A document providing detailed instructions for the execution of one or more test cases.

Test Script: Commonly used to refer to the instructions for a particular test that will be carried out by an automated test tool.

Test Specification: A document specifying the test approach for a software feature or combination or features and the inputs, predicted results and execution conditions for the associated tests.

Test Suite: A collection of tests used to validate the behavior of a product. The scope of a Test Suite varies from organization to organization. There may be several Test Suites for a particular product for example. In most cases however a Test Suite is a high level concept, grouping together hundreds or thousands of tests related by what they are intended to test.

Test Tools: Computer programs used in the testing of a system, a component of the system, or its documentation.

Thread Testing: A variation of top-down testing where the progressive integration of components follows the implementation of subsets of the requirements, as opposed to the integration of components by successively lower levels.

Top Down Testing: An approach to integration testing where the component at the top of the component hierarchy is tested first, with lower level components being simulated by stubs. Tested components are then used to test lower level components. The process is repeated until the lowest level components have been tested.

Total Quality Management: A company commitment to develop a process that achieves high quality product and customer satisfaction.

Traceability Matrix: A document showing the relationship between Test Requirements and Test Cases.

Usability Testing: Testing the ease with which users can learn and use a product.

Use Case: The specification of tests that are conducted from the end-user perspective. Use cases tend to focus on operating software as an end-user would conduct their day-to-day activities.

Unit Testing: Testing of individual software components.

Validation: The process of evaluating software at the end of the software development process to ensure compliance with software requirements. The techniques for validation is testing, inspection and reviewing.

Verification: The process of determining whether of not the products of a given phase of the software development cycle meet the implementation steps and can be traced to the incoming objectives established during the previous phase. The techniques for verification are testing, inspection and reviewing.

Volume Testing: Testing which confirms that any values that may become large over time (such as accumulated counts, logs, and data files), can be accommodated by the program and will not cause the program to stop working or degrade its operation in any manner.

Walkthrough: A review of requirements, designs or code characterized by the author of the material under review guiding the progression of the review.

White Box Testing: Testing based on an analysis of internal workings and structure of a piece of software. Includes techniques such as Branch Testing and Path Testing. Also known as Structural Testing and Glass Box Testing.

Workflow Testing: Scripted end-to-end testing which duplicates specific workflows which are expected to be utilized by the end-user. Click here to continue Reading this post.

Exploratory Testing

24 Apr

Table of Content

1.Introduction
2.All testers do this…
3.Study the new project
4.Choosing Approach
5.Choosing the Executors
6.3 stages of Exploratory Testing
7.Summarizing and evaluating: merits and demerits
8.Conclusion

Introduction
When you first meet the concept of the exploratory testing you can think that its name fully exposes the sense of this sort of activity. But if you get a little bit deeper – this confidence weakens and disappears. Especially clear it can be seen when balancing between the concepts of the exploratory and wild testing, which in one hand are synonyms in QA industry, and in another  (from the good sense point of view) – contrary one to another. It’s because what can have in common the exploration – serious, responsible and well-organized process – and something wild and chaotic, that is wild testing?

And nevertheless I would say that these two types are much interconnected. It is possible even to say that the wild testing is a subset of the exploratory testing, as the last one is very powerful tool, which is used for any software product, as probably no other type of testing is. You can’t start working with any application without it. Even without realizing that, a tester makes first steps in working with a product according to the written and unwritten rules of the exploratory testing.

So what is exploratory testing, when and how it is utilized, what are its goals, approaches,  benefits and penalties?

We’ll discuss everything that in this article.

All testers do this…
The exploratory testing is the only type of testing which does not have a certain scenario. There are no documented Test Plan and test cases. All of scenarios are born in the tester’s mind just in the process of testing and are executed at once. Here is the main difficulty of the process – you should have a considerable base of knowledge and experience.

The main purposes of the exploratory testing are study of the software product (if it’s the first time when tester works with it) and search for the cases untaken into account in the test documentation (if it’s not the first session of work). Watching the program, you hypothesize about its possible behavior, the variants of its responses to your actions and then check up these hypotheses.

And however you can’t do it without a plan. To make the testing more effective it is recommended to create the check-list which will guide you. It’s not obligatory to have it written down but it’s strongly recommended to bear it in mind.

The ideal variant of realization of the exploratory testing is drafting and passing user-cases or tests, which are maximally close to the actions usually performed by user.

If it is the first time when the program is tested, then putting yourself on the user’s place you can find out the most critical bugs for the application functioning. And even if it’s not the first time you work with an application it’s useful to think like a user. The more time tester spends with developers the more he adopts their way of thinking and move away from user. The situation is aggravated by the shortage of time for testing. The more systematic character has the execution of test sets and the less time team has for it the less fantasy is shown by the tester. It’s hard to meet the schedule when you find an «interesting» situation and start to experiment. As the result the vision of the project stiffens, associations become very specific and linked to the concrete steps and terms. It is difficult to find something new or do the same in other way with such adaptation.

So, performing the exploratory testing always try to think in the way a user thinks!

During the testing you should not limit yourself by some rational scopes or paradigms – in fact users very often perform very inefficient actions which can have some unpleasant results.

Try to analyze, what functionality is utilized more frequently and what is touched much rarer. This information will help you to distribute your attention among different features.

The important initial stage of the exploratory testing is formulating the goal. Ask yourself: «Why do I do it? For what purpose?» After completing the testing try to measure your success.

The list of the most widespread goals

  • Study of the new product;
  • Exposure of omissions in the test-plan. The result is to add non-standard tests to the test coverage;
  • Performing the testing of the project with incomplete or inexact specification or when the specification is absent;
  • Research of the specific defect;
  • Improvement of the product quality after completion of the basic (for example, functional) testing.
  • Study the new project

Mostly common the exploratory testing is used as the tool for the study of the new project or functionality.

In this situation you should try to learn all accessible information before starting the testing process.

Documentation is on the first place, as usual. If it’s present, of cause… Specifications, requirement specifications will always remain the faithful helpers of tester.

If consider the process of the exploratory testing as the building of a house, then the documentation is its reliable foundation.

The second step is to ask developers and project managers. They always possess necessary knowledge about the project, therefore do not ignore ANY useful information, ask them questions. My experience shows that this meeting can considerably change your priorities and add new test cases.

Choosing approach
The next stage in building of our house is to choose a project. How we will build? What materials will be used? Where will windows and doors be?

Returning to the QA industry terminology we should choose testing approach. There exist a lot of them, we will consider a few basic ones:

Basic functionality. It is especially important when we have tough time constraints. In this case we shouldn’t get into details and get stuck in some little things. First of all it is necessary to check up main functionality and make sure in its capacity for work.
Places where bugs appear the most frequently. Such places can be the new functionality or those parts of the program which are the most frequently rebuilt. Certainly, this approach is applicable only in case if it’s not the first time you work with the program, and already know its thin places.
The simplest use-cases (for the new build validation). If you’ve got the new version, or version after the deep refactoring then don’t be too lazy to check up the most ordinary use-case, and if it fails return this version to the developers with confidence.
Set of the “favorite” bugs. It will work if the tester knows the programmer well. Each developer has the set of the “favorite” bugs – and each software solution has. When there is much experience of testing even the exploratory testing can be performed by the algorithm.
Concentration on everything and on nothing concretely.  This approach is slightly philosophical. Begin to work with the application as a user and concentrate your attention on everything and on nothing concretely. It’s just like you watch from the outside what is going on. Don’t try to analyze anything while working but be ready to start the analysis at any moment and reproduce all of the steps.
Vulnerability. Those who know the design and UML will get it easier. The schematic model of the project is created, and the weakest place is determined using different methods and approaches. Analysis can be performed from the position of user, architecture or realization. Unlike the usual test design here we analyze the specific model – mixture of architecture of business processes and human perception.

Choosing the executors
So we chose the project for our house J. Next question is about the workers. Who will be assigned to this responsible task?

The first are QA specialists. When choosing the responsible tester you should estimate his experience. It is not inconceivable that assigning an inexperienced man to perform the exploratory testing of the new product you will spend time for unavailing mouse clicking.

It is good to get not only QA specialists to take part in the exploratory testing but also other team members, for example developers. Frequently a tester thinks deeper than a user usually does and so sometimes he complicates a task while not seeing the most obvious errors. The exploratory testing will be good here with its fresh look to the situation.

After performing the regression testing of the product many companies invite independent experts who perform the exploratory testing, simulating the behavior of end users. Expenses on such testing usually justify themselves, as far as critical bugs will be found and fixed before the release.

3 stages of exploratory testing

Watch Out! Construction Work!

Many sources describe the process of the exploratory testing as the following cycle of actions:

study of the product -> planning of tests ->  implementation of tests

And everything this, as already mentioned higher, is not fixed in documents but takes place only in the tester’s mind. It is another argument in behalf on that the exploratory testing should be performed by really experienced specialists: it is the only type of testing, which includes 3 stages of testing of software product simultaneously.

The following questions can help in the process of planning of tests:

  • And what will happen if …?
  • And how the program will respond on such my actions?
  • What data can I get?

Summarizing we can say that the slogan of the exploratory testing is: «Imagine the problem, and then find it».

Summarizing and evaluating: merits and demerits
Walls are ready. Just one small thing is left to do– to construct the roof.

In this section we’ll sum up and, as a result, describe pluses and minuses of the exploratory testing.

Merits of the exploratory testing:

1.Exposes functionality, uncovered by tests;
2.Helps to find the skipped bugs;
3.Allows to look at the product from the end user point of view;
4.Helps to realize the mission of the tested product, improves understanding of it;
5.Requires little preliminary work as far as it’s not too formalized;
6.Helps to find out the majority of critical bugs almost at once;
7.It is acceptable in terms of lack of resources;
8.Discovers usability bugs.

Demerits of the exploratory testing:

1.It is impossible to estimate time for this testing, and, consequently, to set the terms of project completion;
2.It is hard to estimate the project if only exploratory testing is used – it is impossible to make statistics of passed and to failed tests, which is one of basic indexes of product quality.
3.There is no other possibility to check up results but just fully retest the project;
4.It’s impossible to review test cases;
5.The exploratory testing never can be performed identically for several times. Some tests will slip out each time, and so there is a risk to skip some bugs;
6.Results depend much on the experience of tester.
Conclusion
You can read music and you can improvise. Any skills suppose, foremost, that you master some basic techniques and also have certain framework to use as a ground of improvisation.

The same is true for the testing. The exploratory testing is improvisation, the highest degree of tester mastery. It is a complex creative process requiring significant efforts. To perform really qualitative exploratory testing tester should have a lot of experience.

Perform the exploratory testing for the first acquaintance with a product, and it will help to study and understand your application.

Execute the exploratory testing simultaneously with the regressive testing – you will promote the quality of your product, discovering the serious non-standard errors just on the testing stage.

Perform the exploratory testing after basic one and you will be able to discover and remove bugs that slipped out before.

SDLC – Systematic Software Development Cycle

24 Apr
SDLC is a systematic and orderly approach to solving problems related to software systems or in other words, we can say it is a structure imposed on the development of a software product.

Domain Analysis: This phase is very important. The more knowledgeable you are about the domain, less the work required. Another objective of this phase is to make the analysts who will later try to elicit and gather the requirements from the area experts or professionals. So, this phase is an important prelude to extracting and gathering the requirements.

Requirement Analysis: The most important task in creating a software product is extracting the requirements. Customers typically know what they want, but not what software should do, while incomplete, ambiguous or contradictory requirements are recognized by skilled and experienced software engineers.
 
Scope Analysis: Once the requirements are gathered from the client, an analysis of the scope of the development should be determined and clearly stated. This is often called a scope document. 
 
Specification: It is the task of precisely describing the software to be written, possibly in a rigorous way. In practice, most successful specifications are written to understand and fine-tune applications that were already well-developed, although safety-critical software systems are often carefully specified prior to application development. Specifications are most important for external interfaces that must remain stable. A good way to determine whether the specifications are sufficiently precise is to have a third party review the documents making sure that the requirements are logically sound.
 
Software Architecture/Design: Architecture is concerned with making sure the software system will meet the requirements of the product, as well as ensuring that future requirements can be addressed. The architecture step also addresses interfaces between the software system and other software products, as well as the underlying hardware or the host operating system.
 
Coding: The design must be translated into a machine-readable form. The code generation step performs this task. If the design is performed in a detailed manner, code generation can be accomplished without much complication. Programming tools like compilers, interpreters etc… are used to generate the code. Different high level programming languages like C, C++, Pascal, Java are used for coding. With respect to the type of application, the right programming language is chosen.
 
Testing: Once the code is generated, the application / software testing begins. Different testing methodologies are available to unravel the bugs that were committed during the previous phases. Different testing tools and methodologies are already available. Some companies build their own testing tools that are tailor made for their own development operations. 
 
Implementation: After the code is appropriately tested and approved, it is made available for business use i.e. moved into production environment.
 
Documentation: An important task is documenting the internal design of software for the purpose of future maintenance and enhancement.
 
Software Training and Support: As a part of the deployment phase, it is very important to have training classes for the software user. Users will have lots of questions and software problems which leads to the next phase of software.

Maintenance: Maintaining and enhancing software to cope with newly discovered problems or new requirements can take far more time than the initial development of the software.

Comparison of different development models

24 Apr

Different Software Development models have different features and properties. Selection of the software development model depends on the nature of project and client. Here, I will try to give a comparison of various software development models with three parameters:

 1. Contribution to Quality

2. Risks Associated

3. Context of adoption

 Model Name: Waterfall Model

Contribution to Quality: Phase End Checks

Risks Associated: Expects a task to be well done in the first go

Context of adoption: When the requirements are structured and competence is high

 Model Name: Software Development Lie Cycle Model (ETVX Model)

Contribution to Quality: Entry task verification exit definition and quality control through feedback.

Risks Associated: Final Product available only after the complete cycle

Context of adoption: When the requirements are quite structured, but scale is large. One may need to go back for rework if required.

 Model Name: Prototype Model

Contribution to Quality: 1. Seeing is believing. 2. Go iterative and involve customer. 3. Produce working models to give faster delivery and have concrete feedback.

Risks Associated: The scrap may go uncontrollable

Sponsored Links: Context of adoption: When needs to try out things before making a commitment to deliver.

 Model Name: Spiral Model

Contribution to Quality: 1. Avoid scrap as well as rework – do right the first time. 2. Analyze risks before undertaking the next enhancement.

Risks Associated: Inadequate experience and subjective method of risk management

Context of adoption: When the scale is large and planned; passed development would give confidence to move ahead or stop as suited.

 Model Name: V-Model

Contribution to Quality: Plan for testing of artifacts much before their actual completion

Risks Associated: Testing techniques applied may remain subjective

Context of adoption: It is a philosophy that can be applied with any other models you choose.

 Model Name: Unified Process Model

Contribution to Quality: 1. Iterative evolutionary use case centric development. 2. Defines workflows and milestones for better project management.

Risks Associated: Identification of phases needs experience.

Context of adoption: When the scale of project is large.

 Model Name: Agile Models

Contribution to Quality: Anytime delivery through flexible design, limited scope and quick reviews.

Risks Associated: Flexible design techniques not well established. The designers lack an understanding of business need for agility.

Context of adoption: When business needs are dynamic and need to be fulfilled immediately.

Becoming an expert in testing without working hard and in 8 simple steps by pradeep

28 Mar

Image

 

Pre-requisite

  1. You must have worked as a tester for a couple of years with some big companies like Microsoft, Google, IBM, Infosys, Wipro, CTS (whatever)
  2. You must have a blog
  3. You must be on an interview panel for your organization or you interview testers
  4. You could also be a testing coach or trainer.

Step 1:

Once you have that…

Think about an animal or a bird type which is not yet used in testing, be it White Mamba, Giraffe, Elephant, Blackbuck, Spoon bill, Parakeet, Dolphin…

If you want to be more imaginative, you may want to think of insects or reptile families like Spider, Tarantula, Gnat, House Fly, Mosquito – Dengue type, Mosquito – Chikun Gunya type…

Note: Monkey, Guerilla, Snake and Rhino are already in use and introduced by other experts. Don’t copy or if you want to, please owe them necessary credits.

Step 2

Once you fix upon an animal, bird or an insect in mind start to think about the connection between them and testing and form a new technique.

Suggestion / Tip based on experience: It is at this moment, you must start making notes.

For example:

If you are going to think about spider, you can think of a technique where testers behave like a spider, first weaving the web (tests) and then waiting for the bugs to be caught on it, while staying at the centre. Once in a while when there are enough bugs to report, the tester moves from the centre and captures those bugs. If the web is destroyed, move on to make another web.

Note: Don’t use the above published example. Someone may google and find out that you are a fake expert.

Step 3

Write a lengthy explanation of your technique and use words and terms that confuses the reader.  For example use words like: Neil Bhors effect, indemnification against ramification, trapezium syndrome, Wurtz Fittigs reaction… that are not often used and even if Googled, people can’t understand what it means.

Experience based tip: If you are married, ask your spouse to read it, and if you hear, “Honey, this is awesome”, you are publishing ready.

Step 4

Publish it on your blog

Most important note: You shouldn’t do the marketing for your blog post.

Step 5

Ask all those testers whom you interview if they know the technique you published in your blog post and reject them if they didn’t. Do this over a period of six months to at least about 100 testers.

Now what those 100 testers will do is to first go Google your technique and try understanding your blog post. As you have obfuscated it, no one would get it, so they would ask experienced testers and experts in forums and groups that claim to discuss testing. The ego of experienced testers and so called experts wouldn’t let them say, “I don’t know this” but instead, they would offer their own explanations to it.

Step 6

Apply to testing jobs and attend interviews. If the interviewer is asking you to explain your own animal / insect / bird technique to you, tell to yourself, “Congratulations!”

Step 7

Quit your job and start writing to conference program chairs telling them you would be willing to do a half day or a full day tutorial on this famous technique. Say it was the “Snake in the Eagle’s shadow technique” you introduced, you could do a one day tutorial and charge as much as what ISTQB training costs.

Some conferences will give you a chance to keynote and from there you are a hero.

Step 8

Consider publishing a book with your technique. Hang out with other bloggers at conferences, buying them beer and tweet saying, “I am meeting @this_tester and he is so cool” or “This guy is one hell of a tester”. They would be so pleased that they would go back and write blog posts on your keynote and technique.

That’s all. No rocket science. By the way, this actually works. Have you been interviewed and been asked about the Monkey, Guerilla, Rhino, Snake, Yellow, Blue, White, Black?

Oops, I left my one horned male mutated rhinocerous testing technique research midway. I am speaking at CAST 2011 and hope to catch you all there. Apparently, James was the Conference chair and he didn’t give me the keynote.

6/9 part II – One Rainy day [My second corporate love story]

18 Mar

One Rainy Day.!!

It’s been raining for the past two weeks, plenty of rain made every day so restless and gloomy. Once I entered into the office I went straight away to my cubical & opened Chrome in my system. [Typing sound] www.facebook.com searched for Samnju’s name and started to type the msg:”Gd morning Samnju I’ve reached office ma.. W r u?!?  Did u had ur breakfast?!? I know u vl be angry with me, my msg booster got over by that time that’s y I couldn’t msg u .I swear you I ll never do this again. I’m waiting for ur msg so badly, Plz msg me when u r free da, luv You Sweet Heart“

Jo: Came to my place in a tensed mood & asked me furiously “Machi today updated account is not logging in da..

Praveen : By seeing his gesture & reaction , I thought I had made a terrible mistake , it took some time for me to realize that nothing went wrong it’s just a minor problem & I replied him in normal voice ,”Ok machi I ll see that, right now I’ve some important work to do”

Jo: With simile “Oh you are watching cricket uh..??!?!?”

Praveen [Mind voice]: [Ayyo Ivan torture thaanga mudiyalae..!]

Praveen: But with a fake smile I replied”No da I’m texting to Samnju ”

Jo: Replied in low voice “oh sorry da machi. U carry on” & then he looked at my monitor for few seconds & went to his place.

I’m Praveen VCR team, working for L cube. Only thing I learned for this Company is “Politics is everywhere even in S/W firms also”. After a few seconds my phone vibrated with a ring. It’s Ramya she said she was waiting near Anna Nagar bus dipo. It was the 4th time in this week she came here to meet me, on the past three occasions I said some reason & avoided her, but this time around I felt guilty for lying to her on the past three occasion & finally decided to meet her. So I filled my early logout tracker with some stories and went to meet her.

I’ve purposely left my bike in office & walked to dipo. She was standing there alone & she is shivering in cold, carrying her hand bag in one hand and a Pink umbrella in another hand.  She came close to me & said with little tears “Finally you came to meet me”.

Praveen: By hearing those words I felt ashamed of myself & words are hard to come by, then I told her “let’s go I ll take u to ur hostel”. It started drizzling now.

With her beautiful eyes she was staring at me without opening her umbrella. I knew she wanted to share mine. I said “It’s already getting dark open up ur umbrella let’s go” she opened her umbrella & we both went to the auto stand

Ramya: I’m feeling very cold da, can we have a cup of coffee plzzz.

But I answered her “NO.!! Straight away” with pain in my heart. With face full of disappointment she dropped her head down & asked me to take her to Nugambakam station.

[After 20mins] We got down at nugambakam and walked slowly towards the station. The station was filled with bunch of people, all the trains were full & I see people carrying umbrella and their belongings. We sat on the bench and she looked at me innocently. Being together for so long of course I know what she is thinking now .I understand how she must feel now. When she came all this way & that too in this kind of weather to meet me and I treated her like a third person. I felt guilty on me once again.

Ramya Rajagopalan, yes that was her full name .The man behind her name is my uncle working in BHEL with my dad. It was in R.S.K higher sec school when I saw her first. That was my 1st day for School, I’m already late and searching for 11e class room nervously. Suddenly I felt something on my shoulder. Then I realized its blue ink which is quickly spreading all over my shirt, with full of anger I looked around & its Ramya 9th std running down the steps with mouth full of apologies “sorry… sorry plzzz” My whole anger turned into pleasant smile & I told her its ok. Then I met her in guitar class, then occasionally in my home .I think in the Month of Dec 2009 when I was in Chennai for my final year project she called and proposed me. But I refused it by saying that “I’ve already found my girl & her name is Samnju” she started to cry continuously. I thought she ll forget me sooner & will move on with her life, but I was wrong , she is still loving me,coz of me only she is doing her engineering in Chennai.

After sometime I left those memories & came back to my real life, I heard a train whistle & it’s just arrived in the station. Ramya slowly stood up & walked towards the coach. She starred at me without stepping inside the coach, she wiped her tears and said to me, “Take good care of yourself da.” I didn’t uttered a word, just nodded my head lightly and walked out of the station towards the bus stop.

–          By the same time in office –

Dinesh: “Hi da vinu, where is Praveen da?!?!”

Vinu:” I don’t know where he went but he left the office to meet someone da machi”

Dinesh:” K then I ll use his system for a sometime machi, need to check some issues in IE10. Do u know which version he is using?!?” After unlocking the system Samnju’s profile came in front with the msg which sent to her recently.

With confusion turned towards vinu and asked “Hey is this samnju da.? Praveen’s lover right?!?!? But….she was..

Vinu: I interrupted dinesh before he completing “Ya she was dead in that train accident” I never expected that my night mare turns towards him. [The scenes in the dream just crossed my thoughts]

Dinesh: Then why the hell he is still messaging to her profile.??!

Vinu: “what to do his loveable memories with her are still alive” replied sadly.

 

My 2nd Short Scribbling

My 2nd Short Scribbling

Mosquito Spy Drones

14 Dec

US Develops Robot Mosquito Spy Drones..!!

Is this a mosquito?No. It’s an insect spy drone for urban areas, already in production, funded by the US Government. It can be remotely controlled and is equipped with a camera and a microphone. It can land on you, and it may have the potential to take a DNA sample or leave RFID tracking nanotechnology on your skin. It can fly through an open window, or it can attach to your clothing until you take it in your home.

Truth Behind UR DOB

4 Dec

If U were born on the 1st, 10th, 19th, 28th of any month U r number 1….

If U were born on the 2nd, 11th, 20th, 29th of any month then U r number 2…

If U were born on the 3rd, 12th, 21st, 30th of any month then U r number 3…

If U were born on the 4th, 13th, 22nd, 31st of any month then U r number 4…

If U were born on the 5th, 14th, 23rd of any month then U r number 5…

If U were born on the 6th,15th,24th of any month then U r number 6…

If U were born on the 7th,16th,25th of any month then U r number 7…

If U were born on the 8th,17th,26th of any month then U r number 8…

If U were born on the 9th,18th,27th of any month then U r number 9…

Number 1

You are smart, straight talking, funny, stubborn, hardworking, honest,
Jealous on competing basis, kind hearted, angry, friendly, authorities,
Famous person…always want to be and regarded as first on people
Position, they are often like to be independent, will never be under
Others, self confident people!

You are most likely to fall in love in the younger age, but will get
Marry when you mature! You are likely to have problems with people who have opposite views
And you are most likely to take revenge over your
Enemies in a long time basis. You are a spender, but you will have a good profession in the future.
If you are guy you will be very popular that everybody will have mental attraction and respect at you.
You can go anywhere from the local shop to the heart of the parliament because you are positive and
Well talented in numerous issues!! But in your life you will always have some people who will work hard
To bring you & your name down. This is undercover!! Coz of your smart behavior you will be hated by some
People too…

Your family life is very cool, you will have a very nice partner &
Wonderful children… You are pioneer, independent & original…

Your best match is 4,6,8 good match is 3,5,7 !!!

Number 2

No matter what, you will be loved by every one coz your ruler is the
Moon and every one loves the Moon. Well.. You are a person who day dream a lot,
You have very low-self confidence, you need back up for every move in your life, you
Are very much unpredictable. Means you do change according to time and circumstances,
Kind a selfish, have a very strong sense of musical, artistic talent, verbal communication.
Your attitudes are like the Moon, comes to gloom and fade away so everybody can expect
Changes in you. You can be a next Mahatma Gandhi who does peace love or you can be a
Hitler who wants to destroy the man kind and peace (I mean in the community and your own home).

If you really have a deep thought about your own believe in God you can
Feel the difference which will make you stronger! Most of the time your
Words are a kind of would be happening true! So without any knowledge
You can predict the situation. You will become poets, writers, any
Artistic business people!

You are not strong in love, so you will be there and here till you get
Marry.. If U r a girl you will be a responsible woman in the whole
Family. If U r a man you will involve in fights & arguments in the family or
Vice-versa. Means you will sacrifice your life for the goodness sake of
Your family…You are gentle , intuitive with a broad vision, a power
Behind the scenes, well balanced People!!!

Your best match is 2 ,5 ,9 no other people can put up with you !!!

Number 3

You are a person of hard hearted, selfish most of the times, religious,
Loves to climb up in your life. You always tend to have lots of problems
Within your family in the early stages but you will put up with everything..
You have the strong word power, pretty happy face.. So wherever you go always
You have got what you wanted!!! And from the birth always wanted to work hard in order
To achieve something.. You will not get
Anything without hard work! When you reach a man/ woman age you want other younger
Once to listen to you because you want younger people to respect people older than them.
You do set so many examples to others. Generally you are not a cool person. It’s not easy
thing dealing with you. A tough player you are! But once you like someone’s attitud! e then
here you go, what can I say? It will be a lasting friendship. You always have respect from others.
Your life seems to have lots of worries and problems but sure they won’t be long.. You will always
have brilliant kids!!! You love the money a bit too much so temptation will push you to endless
trying and trying.. If you are a guy then it’s over. Looking after your family and help friends, so you
will spend a life time just being generous and kind (except 21st born men). And number 3s you will
be such an example of how to be in the culture & life!!! If you are girl then you have good character
and culture & hardworking attitude. You always follow. You are a freedom lover, creative, ambition
focused, a person who brings beauty , hope & joy to this world!!!

Your best match 6 ,9. Good match 1 ,3 ,5 !!!

Number 4

You are very stubborn too, very hard working but unlucky in important
matters in life, very cool, helpful, you have rough word power.. Might
put lots of people away from you, you may cause nuisance to others if you are a man,
and you often understands others and their problems well. If you are a girl you are very
good with studies and arts. If you are a guy you spend most of the time after girl friends
(almost) at times, you will have sort of too much fun life with mates & girls. Your friends will
spend your time & money and get away with their life and you will become empty handed and
don’t know what to do… So be careful!! You love to spend anyway!!! Your good will is you are
always there to help family and friends. Tell you what you people are little gem! s, specially the girls..
You always fall in love in younger age as well. You often live with disappointments, for an example
you have got a degree in some thing… but you will be unemployed.. or will do very ordinary jobs.
But you will take care of your family very well…All you need to be careful of people who will take
advantage of your kind heart. And beware of your relations too.. You are radical, patient, persistent,
a bit old-fashioned, you live with foundation & order…

Your best Match 1, 8. Good match 5 ,6 , 7 !!!


Number 5

You are very popular within the community, you can get things done by
just chatting..to even enemies! You have a pretty good business mind, you are often
have no-idea what is today is like, or tomorrow is like, you are a person who does anything
when your head thinks “lets do this”. You will be famous if you open up a business,
get involve in share dealings, music etc.. Very popular with sense of humor ,you are
the one your friends and families will always ask for help, and you are the one actually
get money on credit and help your friends. You will have more than 1 relationship,
but when u get settle down you will be a bit selfish anyway. Coz your other half will
have a pretty good amount of control in you, be careful! You tend to go for other relationships!
Contacts even you are married at times ‘coz your popularity.. You are someone who get along
with anyone coz the number 5 is the middle number.. Changes & freedom lovers you are! You are
an explorer with magic on your face. You learn your life through experience and it’s your best teacher!!!

Your best match 1 ,2 ,9. Good match 6 ,8 !!!

Number 6

Ooopppss..you are born to enjoy.. You don’t care about others. I mean
you are always want to enjoy your life time, you are a person.. You will be
very good in either education or work wise or business management! You are talented,
kind (but with only people who you think are nice), very
beautiful girls and guys, popular and more than lucky with anything in
your lives. All the goodness does come with you. Your mind and body is just made perfect for love.
You are lovable by any other numbers. But if you are a number 6 man, you will experience kind of
looks from most girls and will involve in more than few relationships until you get married. If you are girl,
most of you will get marry/engaged early. You are ! a caring
person towards your family & friends . If you miss the half-way mark then you are about to suffer physically
and mentally. Generally you will lead a very good inner-home happiness with nothing short of. You are a person of compassion, comfort & fairness, domestic responsibility, good
judgment, and after all you can heal this world wounds to make peace for every life coz you have the great
power of caring talent to make this world of love one step further…

Your best match 1, 6, 9. Good match 4, 5!!!

Number 7

You have got the attraction to anyone out there, you are realistic,
very confident, happy, such a talented individual with your education,
music, arts, singing, and most importantly acting too. You have real problems
with bad temper! If you are a girl, you are popular with the subjects listed above.
You give up things for your parents. I mean you value your family status a lot, you will be
in the top rank when you reach a certain age. If you are a guy you are popular with girls,
you are a very talented too. Most of the number 7s face lots of problems with their marriage life.
Only a very few are happy. You have everything in your life, but still always number 7s have some sort of unfullfilness, such worries all their lifetime. It’s probably the Lord given you al! l sort of over the
standard humans talents and you are about to suffer in family life. So you need to get ready looking
for a partner rather than waiting. If you don’t, then you might end-up single. So take care with this issue,
ok? You are wonderful, friendly, artistic, happy person.. You are born to
contribute lots to this world!!!

Your best match is 2. Good matches are 1,4 !!!

Number 8

You are a very strong personality, there’s no one out there will
understand you. You are very good at pointing your finger at some thing and say “this is what”.
You are more likely to suffer from the early ages. I mean poverty. If your times are not good
you might lose either of your
parent and end up looking after your entire family. You often suffer all the way in life.
The problems will not allow you to study further, but you will
learn the life in a very practical way. You are the one who will fight
for justice and may die in the war too. You are normally very reserved with handful of
friends and most of the time live life lonely and always
prepared to help others. Well. once you get married (which is often
late) then your bad lucks will go away a bit and you! u become safe. You will face un-expected
problems such as : the error, government, poisonous animals, accidents. You are some one with
great discipline, persistence, courage, strength which will take you to success. You are a great part
of a family team. You are a fighter!

Your Best match 1 ,4, 8. Good match 5 !!!

Number 9

Hey…you guys are the incompatibles people in the world. You are so
strong, physically and mentally… You are often have big-aims. You will work
hard and hard to get there.
Normally you suffer in the early age from family problems and generally you
will have fighting life.. But when you
achieve what you have done, it’s always a big task you have done! You are so much respected in
the community, you are a person who can make a challenge and successfully finish the matter off.
You are very naughty in your younger age, often beaten up by your parents and involve in fights
and you seemed to have lots of injuries in your life time. But when u grow you become calm and macho type.
Love is not an easy matter for you. You are good in engineering or banking jobs coz people always trust you.
Your family life is very good, but will have worries over your children.
Your such qualities are humanitarian, patient, very wise & compassionate.
You are born to achieve targets and serve every one all equally without any prejudice.
You are totally a role model to anybody in the world for a great inspiration.

Your Best match 3, 5, 6, 9. Good match 2

Dream [6/9] by VinuPriyan

4 Dec

Image

6/9

Chennai Egmore:

I lighted a cigarette and was staring at the station seriously in a confused state.

Thinking about that dream.  After some time I heard a voice calling “Vinu…Vinu…”.

It was my friend Praveen waving his hands towards me and shouting my name.

He came near me and started scolding “How many times I have to call u idiot? Are you in this world or not?”

I came to the reality. Am Vinu Vignesh. Am an ECE student.  Am a cool guy but I hate programming.  The words like “Coding”, “Scripts” are bitter most words in my life. Hence to escape from it I did a Software testing course and joined a private firm “L-Cube” as a software tester at Chennai before 2 years. A week before our 2 years bond to the company was over and by God’s grace before that

am placed in a MNC. Hence I quitted my former company and going to my native to enjoy

for some days for a change before I join in new company. Praveen and Malai are my best friends in my company and my roommates too. We three are going together to our homes.

Everything was going fine till yesterday. But the dream which I got yesterday night was the reason for my behavior. On seeing the confusion on my face Praveen asked me “Vinu are you still thinking about the same dream?” Another guy Malai added “Hey dudes we can direct Final destination 6 with your story da”. I was speechless. But I added to my part “Hey no dudes It was so real….”.Praveen got tensed and said “Hey what are you blabbering da! 6 o clk… Red dressed baby… Train accident… Enough da it’s just a dream”.  I too felt am going mad on thinking about that and told “Hmmm whatever I say u both will tease me with a Hollywood movie name …Leave that. Let’s start” and put an end to the conversation.

We all were sitting in the couches inside the station. I started seeing my watch and the railway track continuously. Suddenly my mobile vibrated. I got a sms. After seeing that message I felt relaxed as if I had a pain killer injection. Because it was from ‘Akalya’.

Yeah her full name is ‘Akalya Rajendran’. To say about her, she is a cute, egoistic and possessive girl. She is working as a software developer in my company. Whenever our team put any error during testing she will just send a mail that everything is working fine in bold font. She does not likes me as am in testing team and obviously because of her “WORKING FINE” mails I don’t like her.

(First impression is best impressiongra  formula work agalana enna boss opposite poles attracts each Other nu oru formula irukula..!! That’s WORKING FINE between us!). Hence we became good friends. My day started and ended with her sweet cute messages. We both started to call each other and that calls ended during midnights. I don’t know whether am loving her.

Praveen shook me and asked me to turn towards him. I turned slowly but after seeing there I felt as though electric shock passed over me. Because a cute girl baby in red dress was playing there. The baby I saw in my dream. Suddenly I saw my watch. It was 6 0 clock. I heard the train horn coming towards the station. I could not explain my feeling. I felt as if as if my heart stopped. I was drenched in sweat. The train neared. On seeing my reactions my friends started laughing. But nothing happened. We three boarded the train. The baby went with her mom.

Praveen: Hey dude nothing is happened. I think the driver is changed. Let’s check the train driver in your dream dude.

Malai: Hey Vinu I recorded all your reactions in mobile. Gonna update in FB. See what is going to happen.

Me: Am a loser uh!!! My God. Its ok dudes. Am happy that nothing happened to that baby.

Usually my dreams will come true. Hence I believed in my dreams. For me dreams are something which indicates something to us. But this time it didn’t happen. We searched our seats and sat. Train started from Egmore. Even though nothing happened I could not become normal as my incense said it will happen for sure. I was in a dilemma.

Our train crossed villupuram. Praveen was speaking with her girlfriend ‘Samju’. Me and Malai felt bored. So I asked him to put a movie in laptop as I want to change my mind. He switched on and put animated batman series. I like super hero ‘Batman’. He is the one who have no super powers. We both are watching “Batman Begins”. I got involved to the movie. And I forgot my terrific dream for some time.           Praveen ended the call and came near me with a smiling face. He said “Vinu be ready to give treat for us da. Malai tell me a good hotel da”. Malai asked “Hey what happened da? Tell the matter da. Depending on that we will select the hotels…” I could not understand what is going on there.

I asked “Hey Praveen first tell me what happened da!”. He said “Ok Ok wait dudes. I will say everything with a proof”. I was waiting curiously what will be the matter. That suspense was broken by the MMS tone in Praveen’s mobile. He opened that MMS. He started the audio file. It was akalya crying to her roommate samju.

Akalya sobbed “Vinu is going to his native samju. Everything came to an end. I seriously love him and I wanna say this to him. But I couldn’t say this to him. If he has rejected my proposal I will convince in some days. But it’s like a hell without saying this to him. I lost him.” She started crying bitterly. Now its samju voice saying “Don’t worry dear I will speak to vinu regarding this. Y u are crying like a baby for this?” Now akalya said “No samju after this if he avoids me I can’t live in this world…” Samju started shouting “What you are coming to say now…..”. The MMS was ended.  I could not believe my ears and I was speechless. I got a mild shake in my heart. A silent tear rolled down my cheeks. I don’t know how to react for this. Suddenly I searched my mobile and went near the door. The air was blowing vigorously. My fingers dialed her number.

Her phone was ringing. At third ring she attended the call. Akalya in her sweet voice spoke “Hey vinu dear why you didn’t message me? Where are you now?”

After hearing her voice I felt to hug her and say I love you too my dear. But I controlled myself and said “No da we all were watching movie in laptop. That’s why I didn’t message you.” I felt a dullness in her voice but to make her laugh I asked” Why your voice is dull dear? They served upma (Indian Food) in your hostel uh???”

She replied “No da now am in egmore station. Going to my home.” I felt somewhat relaxed that she is going to her home and asked the train details. She said “9 o clock train da.  Coach D13.”

While I was speaking with akalya my friend gestured me to switch off the lap. I felt to see the climax. So I said to her “Dear be in line for 2 minutes. I will be back”. She got angry it seems. She said Ok I will wait in a stern voice. I smiled and butterflies started flying in my heart.

I went to my friend and asked what happened to the story. He told that Batman will be locked in a dream world by the joker. But batman does not know he is in dream. But after seeing the books in that library batman comes to know he is in dream world”. I stopped Malai and asked “Hey dude how he found in library da?”.  He replied “In library books everything was upside down in dream da.  So he found that”.

While he was saying this to me something strikes in my mind. My face turned pale L.  Suddenly I took my mobile and shouted akalya……………… akalya…………  She did not respond. I could hear a girl baby voice and akalya voice. She is in train. Then she spoke “Sorry da vinu… I was playing with a cute little girl. That’s why I didn’t see my mobile. She is so sweet and cute in red dress da.”  I turned my watch slowly.

Its sharply showing 9. Then I realized that the time that came in my dream was not 6. Its 9. I shouted in phone “Akalya….. Please go away from there……!!!!” Then I heared a terrific sound like a thunder.  I could not hear anything… Finally I heard the crying sound of my akalya…………………… The call was disconnected. L L L

And my deep sleep was also broke by a vibration of my mobile. I opened my eyes and saw my mobile. It showed “1 text message “. It was from akalya “Good Morning da Pappu. Wake up its time to get ready to