Common Problems with Testing? - Interview question asked in Syscom, Noida

Common Problems with Testing?
There are major problems with the efficiency and effectiveness of testing as it is currently performed in practice. In the course of three decades of developing systems and software—as well my involvement in numerous independent technical assessments of development projects—I have identified and analyzed testing-related problems that other engineers, managers, and I have observed to commonly occur during testing. 


The large number of testing problems necessitated that they be categorized. At the top level, these problems were organized into two groups
general testing problems that are not specific to any type of testing, but apply to all different types of testing 
test type-specific problems that are specific to a single type of testing such as unit testing, integration testing, and system testing.

The remainder of this post will focus on general testing problems, which can be divided into eight categories:

• Test planning and scheduling problems often occur when there is no separate test plan, but rather highly incomplete and superficial summaries in other planning documents. Test plans are often ignored once they are written, and test case descriptions are often mistaken for overall test plans. The schedule of testing is often inadequate for the amount of testing that should be performed, especially when testing is primarily manual. Significant testing is often postponed until too late in the development process, especially on projects using traditional sequential development cycles.
• Stakeholder involvement and commitment problems include having the wrong testing mindset (that the purpose of testing is to show that the software works instead of finding defects), having unrealistic testing expectations (that testing will find all of the significant defects), and having stakeholders who are inadequate committed to and supporting of the testing effort.
• Management-related testing problems involve the impact of inadequate management. For example, management can fail to supply adequate test resources or place inappropriate external pressures one testing. There may be inadequate test-related risk management or test metrics. Testing lessons learned are far too often ignored, so the same problems are repeated project after project.
• Test organizational and professionalism problems include a lack of independence, unclear testing responsibilities, and inadequate testing expertise.
• Test process problems often occur when testing and engineering processes are poorly integrated. Organizations sometimes take a “one-size-fits-all” approach taken to testing, regardless of the specific needs of the project. Testing may not be adequately prioritized so that functional testing, black-box system testing, orwhite-box unit and integration testing may be overemphasized. Testing of components, subsystems, or the system may begin before they are sufficiently mature for testing. Other problems include inadequate test evaluations and inadequate test maintenance.   
• Test tools and environments problems include an over-reliance on manual testing or COTS testing tools. Often, there are an insufficient number of test environments. Some of the test environments may also have poor quality (excessive defects) or insufficient fidelity to the actual system being tested. Moreover, the system and software under test may behave differently during testing than during operation. Other common problems are that tests were not delivered or the test software, test data, and test environments were not under sufficient configuration control.
• Test communication problems primarily involve inadequate test documentation. These types of problems often occur when test documents are not maintained or inadequate communication concerning testing is taking place.
• Requirements-related testing problems are related to the requirements that should be driving testing. Often, the requirements are ambiguous, missing, incomplete, incorrect, or unstable. Lower-level requirements may be improperly derived from their higher-level sources. Likewise, verification methods may be unspecified and the tracing between requirements and tests may be lacking.

Can you tell me the difference between smoke and system testing? Interview question asked in CSC, Noida

tell me the difference between smoke and system testing?

 • A smoke test is specialized system test to verify that system will not have a critical failure, usually done after significant changes or a new code release. System testing is much more comprehensive and done after the smoke test passes (always considering the time constraints that you are under).

• Smoke testing is perform to verify the critical features of an application while in system testing is done to thoroughly test the application and verify all aspects not only critical or basic features.And also system testing is performed on environment similar to production environment.

Regression Testing, Smoke Testing and Sanity Testing? - Interview question asked in Naggaro

Which come first to next place in testing Regression Testing, Smoke Testing and Sanity Testing?

Smoke Testing - 

1) A Smoke test is designed to touch every part of the application in a cursory way. 
2) Smoke testing is conducted to ensure whether the most crucial functions of a program are working 
3) Smoke testing is normal health check up to a build of an application before taking it to testing in depth. 

Sanity Testing - 
1) A sanity test is a narrow regression test that focuses on one or a few areas of functionality. Sanity testing is usually narrow and deep. 
2) Sanity testing is a cursory testing, it is performed whenever a cursory testing is sufficient to prove the application is functioning according to specifications. 

Regression Test - 
1) The intent of regression testing is to provide a general assurance that no additional errors were introduced in the process of fixing other issues.

 System Testing:- It is end to end testing.Where testing environment is just similar to production environment.here we check 1.Region Specific 2.Page Specific 3.Text Specific 4.Time duration specific 5.Cost specific. 

We start system testing when- minimum number of features are ready. 
basic functionality of all the module must be working.

a. Smoke Testing : To make sure the build is not breaking and can be testable. 
b. Sanity Testing : To check the basic functionality without going into detail. 
c. Regression: To make sure the existing functionality is not been impacted because of new changes.

 First smoke test checking basic availibility 
Then sanity check: basic functionalities work as required 
then regression test : control all desired functionalities

Hiring Wisdom: Top 10 Ways to Guarantee Your Best People Will Quit

10 Ways to Guarantee Your Best People Will Quit...

Here are 10 ways to guarantee that your best people will quit:

10. Treat everyone equally. This may sound good, but your employees are not equal. Some are worth more because they produce more results. The key is not to treat them equally, it is to treat them all fairly.

9. Tolerate mediocrity. A-players don’t have to or want to play with a bunch of C-players.

8. Have dumb rules. I did not say have no rules, I said don’t have dumb rules. Great employees want to have guidelines and direction, but they don’t want to have rules that get in the way of doing their jobs or that conflict with the values the company says are important.

7. Don’t recognize outstanding performance and contributions. Remember Psychology 101 — Behavior you want repeated needs to be rewarded immediately.

6. Don’t have any fun at work. Where’s the written rule that says work has to be serious? If you find it, rip it to shreds and stomp on it because the notion that work cannot be fun is actually counterproductive. The workplace should be fun. Find ways to make work and/or the work environment more relaxed and fun and you will have happy employees who look forward to coming to work each day.

5. Don’t keep your people informed. You’ve got to communicate not only the good, but also the bad and the ugly. If you don’t tell them, the rumor mill will.

4. Micromanage. Tell them what you want done and how you want it done. Don’t tell them why it needs to be done and why their job is important. Don’t ask for their input on how it could be done better.

3. Don’t develop an employee retention strategy. Employee retention deserves your attention every day. Make a list of the people you don’t want to lose and, next to each name, write down what you are doing or will do to ensure that person stays engaged and on board.

2. Don’t do employee retention interviews. Wait until a great employee is walking out the door instead and conduct an exit interview to see what you could have done differently so they would not have gone out looking for another job.

1. Make your onboarding program an exercise in tedium. Employees are most impressionable during the first 60 days on the job. Every bit of information gathered during this time will either reinforce your new hire’s “buying decision” (to take the job) or lead to “Hire’s Remorse.”

The biggest cause of “Hire’s Remorse” is the dreaded Employee Orientation/Training Program. Most are poorly organized, inefficient, and boring. How can you expect excellence from your new hires if your orientation program is a sloppy amalgamation of tedious paperwork, boring policies and procedures, and hours of regulations and red tape?

To reinforce their buying decision, get key management involved on the first day and make sure your orientation delivers and reinforces these three messages repeatedly:

A. You were carefully chosen and we’re glad you’re here;

B. You’re now part of a great organization;

C. This is why your job is so important.

This was originally published in the April 2013 Humetrics Hiring Hints newsletter.

Mel Kleiman, CSP, is an internationally-known authority on recruiting, selecting, and hiring hourly employees. He has been the president of Humetrics since 1976 and has over 30 years of practical experience, research, consulting and professional speaking work to his credit. Contact him atmkleiman@humetrics.com.

 http://www.tlnt.com/2013/04/08/hiring-wisdom-top-10-ways-to-guarantee-your-best-people-will-quit/?utm_source=twitterfeed&utm_medium=linkedin&utm_campaign=Feed%3A+tlnt+%28TLNT%3A+The+Business+of+HR%29

Test Planning

Test Plan - The Strategic side of Testing

There are many software organizations where the term QA refers to a group of testers who randomly receive builds from the developers and proceed to ―play‖ with the system in order fish out the bugs. In some cases these engineers use some informal flows or scripts to base their tests but these documents are not even close to a testing strategy or test plan of any sort.

We all agree that one of the main objectives of the QA team is to rid the product of the most important and disruptive bugs, but doing it completely Ad-Hoc and without a good preparation is the most ineffective and inefficient way to go about this process.

The common testing project is composed of 4 phases:
a. Planning
b. Preparation
c. Execution
d. Post-analysis
In this post I will focus on the planning stage, since I believe this is the most important phase and the one that we take for granted the most.

So now we can start with 2 big questions:
- What do we need to plan?
AND
- How do we go about planning it?
The answer to both questions is the Test Plan (also known as Software Test Plan, Testing Strategy, etc). The Test Plan is both a document and a process; by this I mean that at the end of the day you will have a document you can look at and admire (you may even hang it on the wall!), but not less important is the process you need to follow to create and communicate all the aspects that conform the document with all its sections.

What makes a good Test Plan?
Each company has different needs and thus each will require a different Test Plan template. The important thing is to understand that this document will represent your Scope of Work  for the specific project. It should be the place where you and your external stakeholders (Product Management, Development, Support, etc) turn to in order to understand what your team is testing and how are they approaching each testing task.
To look at it in a simple way, imagine your company decides to outsource all its testing tasks to an external group (your group) and you need to put together a contract explaining what your team will do and what will it need in order to do it. Like all contracts, the idea is to review all the details and agree on them before signing the deal (or starting the project).

Following are the usual sections I include in my MTPs (remember to take them only as a suggestion and to modify them based on your needs!):

1. Objectives of the testing process:
The objectives of the testing process depend on the nature of the development project. Examples of testing objectives are: new feature validation, additional configuration certification, translation validations, installation and/or upgrade testing, etc.
Just make sure you don‘t write trivial stuff like: to find all the bugs in the system or to assure we release a quality product.
This section is to communicate what YOU will be thinking when planning and running your tests.

2. Testing scope:
For many people the testing scope is the heart of the Master Test Plan. It describes the things you will focus in each of the application areas and/or features to test. I tend to make this section a nested list, and for each item I describe:
- The main aspects to tests
- The product risks or potential bugs I foresee
- Concrete faults or main scenarios to validate
- Assumptions or requirements (documented API, stable GUI, etc)
- And any other aspects worth mentioning regarding the specific area under test.
This is the place where you provide your stakeholders with the information about what will you be testing on each section of the product, and here is also where you should look for comments and suggestions from developers, product architects, support engineers, fellow testers, etc.

Some Test Planning go the extra mile and provide a list of areas and features that are Out of the Scope of the testing process.

3. Testing configuration matrix:
Your application surely needs to support a defined number of configurations and platforms, here is where you should list these configurations together with the testing matrix you will run in order to validate it.
Keep in mind that by configurations we may refer to different things for different projects; on one project it may be Operating Systems and Browsers, while on another project it is additional product-components and specific versions required by your product to function correctly.
In any case, by configuration we mean the environmental (and thus external) parameters required by our system to work.
www.teatimewithtesters.com December 2012|43
In the cases when the list of officially supported configurations is more extensive than the systems you plan to test you should provide 2 separate lists:
(a) The list of theoretically supported configurations, as specified by your customer or product management team.
(b) The list of actual configurations you will test in order to achieve the above level of support, together with the distribution or percentage of tests that will be run on each.
In order to do this I suggest a presentation format and planning method similar to what I described in my last post.

4. Required Hardware / Software
Based on the testing scope and the required configurations you need to create a list of all the hardware and software resources you will need to complete your tests.
In addition to special machinery and/or licenses, this is the place to ask for specific stubs or simulators you may require during your tests.
If you plan to use automation of any sort include the number of software licenses as well as the amount of virtual users you will need for load and performance testing.

5. Testing preparations
By now it should be clear what you want to test, now you need to understand what preparations to do in order to test it.
For this point should make a high level review of your test plan inventory and compare it to your testing scope. You should end with tree lists of tests:
(1) Tests that are ready to be run as is
(2) Tests that need to be reviewed and/or updated to match the changes to the functionality
(3) Tests you need to write from scratch
For each list assign the amount of time you will require to work on the tests; you can also include the information and/or help you will need from other teams.
If you also need time to prepare testing environment or create testing data this is the section where to add this additional preparation costs

6. Testing schedule:
(The favorite section of all our Project Managers!)
Our operations are usually divided into stages and cycles. For example a project may have a preparation stage, an execution stage composed of 3 to 5 testing cycles, and a final product release stage/cycle.
For each one we should provide at least the following information:
(a) Expected time lines
(b) Entry and exit criteria
(c) Testing scope & objectives
(d) Testing resources (peopleware, software and hardware)
and any additional information pertaining to the specific cycle.

7. Testers & schedules
Following on the project side of the MTP you should list all your testers and the dates when they will be available for your project. List holidays, vacations, training and any other activities that may have an impact on the availability of a resource.
If part of your tester-resources will be new make sure to account for the training and ramp-up time they will require at the start of their work.

8. Risks
Like every project you should list the risk you may encounter. Examples of risks are difficulties in recruiting resources, instability of the product that may delay your schedule, high attrition rates, etc.
Each risk should include the following information:
(a) Person in charge of the risk
(b) Severity and likelihood of the risk materializing
(c) Dates of relevancy when the risk may materialize
(d) Consequence of the risk materializing
(e) Prevention & contingency plans

9. References & attachments
Add links to any additional documents and/or information referent to the project.
Add also a list of all the contact persons as well as their areas of responsibility.
A final word of advice - Some companies and processes are not ready to handle a full blown MTP, specially start-ups and/or companies working under less structured development process (e.g. Agile Development).
If you work on one of these companies it doesn‘t mean that you can or should work without a strategic QA plan, it simply means that you need to mold it in order for the plan to meet your company culture and way of life.

www.texira.com

Tea Time With Tester

Tea Time With Tester 

www.teatimewithtester.com

www.teatimewithtesters.com
I m the big fan of Tea Time With Tester  " first website provide free online magzines for testers only www.teatimewithtesters.com " i like it boss...hats off for your and your team members work..keep writing and we
Here i found the most common thing which everyone must knows that each and every companies have there own development & testing cultures and taste..so keep reading magzines from " www.teatimewithtesters.com ".

I'm with most folks here. this isn't the kind of place where this extensive subject can be addressed as you have asked besides we have no real context to work with. Every organization has a culture, the Testing needs to fit into the culture you are in as well as achieving an objective (or set of objectives). We don't know the user base, organizational goals and objectives, risks, is it cloud based or not, is it built on a commercial platform or built from scratch, etc, etc, etc.

May I ask the purpose of the discussion?

www.texira.com

Web Testing

Web Testing:

Check List for Web Testing:
1. Functionality testing

2. Usability testing

3. Interface testing

4. Compatibility testing

5. Performance testing

6. Security testing

for Clear cut description check below link..
http://www.softwaretestinghelp.com/web-application-testing/
www.teatimewithtesters.com
Author

Web Application Functionality testing

Web Applications testing process or web application functionality testing

I believe while testing a new application, we should perform a round of smoke testing just to get an idea that the major functionality is working. This can be achieved by clicking all the present links on the website, this will give an idea if there are any broken links. Also if all the pages are getting navigated as per the specifications. This round of testing minimizes the risk of getting the show stoppers at the last moment and hence saves times and money.

Then we come to the functional testing. Here we test the functionality of the web application. We execute our functional test cases to test if all the pages are working as per the specifications. Functional testing is generally combined with system integration testing so interface and usability testing or compatibility testing can also be tested at the same time. There are two aspects of testing here

Static – Page level validation is done here like cosmetic. Spell check, page name, color, text format, buttons on the page etc come in this category. We just have to open that page in a website in order to perform static testing.

Dynamic – Here we test the functionality of that particular page by actually executing that. We perform few actions in order to check the output. And this has to be done in +ve and negative way both.

Hope this helps

Regards
Ishaa Awasthi

Web Application testing "Interview question asked in Aricent?

Web Application: what are the steps to test a website  or how to test a website

There are various ways and it's like question of what contains in Manual Testing. 
According to me, 
1. If the Application is not ready and 'in-progress' phase 
- Tester can devide application in various modules where a particular major functionality is covered. We have Business Specification Documents, Functional Specification Documents with Workflow stated. 
- Try to understand those and figure out how would the application look like as mentioned in the flow. There may be 'mock-ups' provided which would help in understanding the application 
- Create scenarios using functional documents, then Create Test Cases. Get them reviewed from your senior. 
- Once the execution is started, execute the test-cases. Have smoke testing to get to know that whatever picture you have created of your project is the same of something made different. 

2. If the Application is ready 
- Again have a smoke testing and understand the flow. Take particular module. and Start Testing. 

Now testing includes functional testing, UI testing, Validations, Positive Scenarios and Negative scenarios. 
If all modules are ready then it's System Testing, Intigration testing. 
For UAT, End-to-End testing. 
For Testing, you need to know which all possible scenarios can happen around the impacts created by modules in a various ways. 
This all I can only write. Rest is upto tester on how deep he/she wants to break the code! :) 
I am still not satisfied what I wrote here cause afterall it all depends upon testers thinking and ways he adopts...!! 
We Hope this helps! 
Thanks!

IPL t20 teams

IPL Teams
" who is your star player"

Chennai Super Kings Squad

Akila Dananjaya, Albie Morkel, Anirudha Srikkanth, Ankit Singh Rajpoot, B Aparajith, Ben Hilfenhaus, Ben Laughlin, Christopher Morris, Dirk Nannes, Dwayne Bravo, Francois Du Plessis, Imtiaz Ahmed, Jason Holder, Michael Hussey, Mohit Sharma, MS Dhoni, Murali Vijay, Nuwan Kulasekara, R Karthikeyan, Ravichandran Ashwin, Ravindra Jadeja, Ronit More, Shadab Jakati, Subramaniam Badrinath, Suresh Raina, Vijay Shankar and Wriddhiman Saha

Delhi Daredevils Squad

Ajit Agarkar, Andre Russell, Arisht Singhvi, Ashish Nehra, CM Gautam, David Warner, Gulam Bodi, Irfan Pathan, Jeevan Mendis, Jesse Ryder, Johan Botha, Kedar Jadhav, Kevin Pietersen, Mahela Jayawardene, Manpreet Juneja, Morne Morkel, Naman Ojha, Pawan Negi, Roelof Van Der Merwe, Royston Dias, Siddarth Kaul, Sujit Nayak, Shahbaz Nadeem, Umesh Yadav, Unmukt Chand, Varun Aaron, Venugopal Rao, Virender Sehwag and Yogesh Nagar

Kings XI Punjab Squad

Adam Gilchrist, Aniket Choudhary, Azhar Mahmood, Bhargav Bhatt, Bipul Sharma, David Hussey, David Miller, Dimitri Mascarenhas, Gurkeerat Mann Singh, Harmeet Singh Bansal, Luke Pomersbach, Manan Vohra, Mandeep Singh, Manpreet Gony, Nitin Saini, Parvinder Awana, Paul Valthaty, Piyush Chawla, Praveen Kumar, R Sathish, Ryan Harris, Sandeep Sharma, Shaun Marsh, Siddharth Chitnis and Sunny Singh

Kolkata Knight Riders Squad

Brad Haddin, Brendon McCullum, Brett Lee, Debabrata Das, Eoin Morgan, Gautam Gambhir, Iqbal Abdulla, Jacques Kallis, James Pattinson, Lakshmipathy Balaji, Laxmi Ratan Shukla, Manoj Tiwary, Manvinder Bisla, Mohammad Shami, Pradeep Sangwan, Rajat Bhatia, Ryan McLaren, Ryan ten Doeschate, Sachithra Senanayake, Sarabjit Singh Ladda, Shakib Al Hasan, Sunil Narine and Yusuf Pathan

Mumbai Indians Squad

Abu Nechim Ahmed, Akshar Patel, Aditya Tare, Aiden Blizzard, Ambati Rayudu, Amitoze Singh, Dhawal Kulkarni, Dinesh Karthik, Dwayne Smith, Glenn Maxwell, Harbhajan Singh, Jacob Oram, Jalaj Saxena, James Franklin, Kieron Pollard, Lasith Malinga, Mitchell Johnson, Munaf Patel, Nathan Coulter-Nile, Philip Hughes, Pawan Suyal, Pragyan Ojha, Ricky Ponting, Rishi Dhawan, Rohit Sharma, Sachin Tendulkar, Suryakumar Yadav, Sushant Marathe and Yuzvendra Singh Chahal

Pune Warriors Squad

Abhishek Nayar, Ajantha Mendis, Ali Murtaza, Angelo Mathews, Anustup Majumdar, Ashoke Dinda, Bhuvneshwar Kumar, Dheeraj Jadhav, Eklavya Dwivedi, Harpreet Singh, Ishwar Pandey, Kane Richardson, Krishnakant Upadhyay, Luke Wright, Mahesh Rawat, Manish Pandey, Marlon Samuels, Michael Clarke, Mitchell Marsh, Mithun Manhas, Parveez Rasool, Rahul Sharma, Raiphi Gomez, Robin Uthappa, Ross Taylor, Shrikant Wagh, Steve Smith, Tirumalasetti Suman, Tamim Iqbal, Udit Birla, Yuvraj Singh and Wayne Parnell

Rajasthan Royals Squad

Ajinkya Rahane, Ajit Chandila, Ankeet Chavan, Amit Singh, Ashok Menaria, Brad Hodge, Brad Hogg, Dishant Yagnik, Fidel Edwards, Harmeet Singh, James Faulkner, Kevon Cooper, Kusal Janith Perera, Owais Shah, Pravin Tambe, Rahul Dravid, Rahul Shukla, S Sreesanth, Sachin Baby, Samuel Badree, Sanju Samson, Shane Watson, Shaun Tait, Shreevats Goswami, Siddharth Trivedi and Stuart Binny

Royal Challengers Bangalore Squad

AB De Villiers, Abhimanyu Mithun, Abhinav Mukund, Andrew McDonald, Arun Karthik, Cheteshwar Pujara, Chris Gayle, Christopher Barnwell, Daniel Christian, Daniel Vettori, Harshal Patel, Jaidev Unadkat, K P Appanna, Karun Nair, Mayank Agarwal, Moises Henriques, Murali Kartik, Muttiah Muralitharan, Pankaj Singh, Prasanth Parameswaran, Ranganath Vinay Kumar, Ravi Rampaul, Rudra Pratap Singh, S Aravind, Sandeep Warrier, Saurabh Tiwary, Sheldon Jackson, Sunny Sohal, Syed Mohammad, Tillakaratne Dilshan, Vijay Zol, Virat Kohli and Zaheer Khan

Sunrisers Hyderabad Squad

Akshath Reddy, Amit Mishra, Anand Rajan, Ankit Sharma, Ashish Reddy, Biplab Samantray, Cameron White, Chris Lynn, Clint McKay, Dale Steyn, Darren Sammy, Dwaraka Ravi Teja, Hanuma Vihari, Ishant Sharma, Jean-Paul Duminy, Karan Sharma, Kumar Sangakkara, Nathan McCullum, Parthiv Patel, Quinton de Kock, Sachin Rana, Shikhar Dhawan, Sudeep Tyagi, Thalaivan Sargunam, Thisara Perera and Veer Pratap Singh

Keywords: IPL 2013 schedule, IPL 2013 fixtures, IPL Schedule 2013, Pepsi IPL 2013, IPL PDF Download, IPL 2013 PDF, IPL 2013, IPL 6 Time Table

IPL Schedule

IPLT20 Schedule Code


Embed Code

<script language="javascript" src="http://www.cricschedule.com/embed.php?id=128"></script>
<noscript><a href="http://www.cricschedule.com/tournament/1/ipl.html">IPL Schedule</a></noscript>

IPL Schedule 2013

IPLT20 Schedule 2013     

The Indian Premier League, or as some would like to address it as the Cricket Carnival is back in the subcontinent and is in tremendous flow with a lot of new exciting surprises keeping viewers hooked to their TV sets. There was much ado about the Pepsico IPL schedule before the start of the event with critics complaining about too much of cricket being played which can fatigue players in the long run. The short version of the game has added a lot of color to cricket itself especially after the involvement of Bollywood superstars in the event. The Pepsi IPL fixture was declared back in the month of January after the auction held at Bangalore. The IPL time table is considered to be a lot more hyped than other tournament time tables owing to the fact that cricket crazy India always tends to promise a better turn out at the stadiums than any other countries in the world. The indian premier league schedule has been carefully designed to ensure optimum crowd turnout and the months of April-May are considered to be the time of the year when cricket in India is played at its best. Top four teams from IPL Points Table will enter playoff/semi final round.

As to what a lot may oppose regarding the busy indian premier league fixtures that has kept the veterans in the hunt still going strong; it does not really spoil the game of cricket but also encourages a lot of talented youngsters to play with conviction. The indian premier league time table this year is hands down devoid of controversies though unlike that of the 4th edition of the league where the IPLT20 schedule was prepared and started just after 4 days from the last match of the ICC Cricket World Cup. 

From http://www.cricschedule.com

Date and Time	Match Details and Series
Wed Apr 3  20:00 local | 14:30 GMT	1st IPL - Kolkata Knight Riders vs Delhi Daredevils  Eden Gardens, Kolkata
Thu Apr 4  20:00 local | 14:30 GMT	2nd IPL - Royal Challengers Bangalore vs Mumbai Indians  M.Chinnaswamy Stadium, Bangalore
Fri Apr 5  20:00 local | 14:30 GMT	3rd IPL - Sunrisers Hyderabad vs Pune Warriors  Rajiv Gandhi Int. Stadium, Hyderabad
Sat Apr 6  16:00 local | 10:30 GMT	4th IPL - Delhi Daredevils vs Rajasthan Royals  Feroz Shah Kotla, Delhi
Sat Apr 6  20:00 local | 14:30 GMT	5th IPL - Chennai Super Kings vs Mumbai Indians  MA Chidambaram Stadium - Chepauk, Chennai
Sun Apr 7  16:00 local | 10:30 GMT	6th IPL - Pune Warriors vs Kings XI Punjab  Subrata Roy Sahara Stadium, Pune
Sun Apr 7  20:00 local | 14:30 GMT	7th IPL - Sunrisers Hyderabad vs Royal Challengers Bangalore  Rajiv Gandhi Int. Stadium, Hyderabad
Mon Apr 8  20:00 local | 14:30 GMT	8th IPL - Rajasthan Royals vs Kolkata Knight Riders  Sawai Mansingh Stadium, Jaipur
Tue Apr 9  16:00 local | 10:30 GMT	9th IPL - Royal Challengers Bangalore vs Sunrisers Hyderabad  M.Chinnaswamy Stadium, Bangalore
Tue Apr 9  20:00 local | 14:30 GMT	10th IPL - Mumbai Indians vs Delhi Daredevils  Wankhede Stadium, Mumbai
Wed Apr 10  20:00 local | 14:30 GMT	11th IPL - Kings XI Punjab vs Chennai Super Kings  Punjab C.A. Stadium, Mohali
Thu Apr 11  16:00 local | 10:30 GMT	12th IPL - Royal Challengers Bangalore vs Kolkata Knight Riders  M.Chinnaswamy Stadium, Bangalore
Thu Apr 11  20:00 local | 14:30 GMT	13th IPL - Pune Warriors vs Rajasthan Royals  Subrata Roy Sahara Stadium, Pune
Fri Apr 12  20:00 local | 14:30 GMT	14th IPL - Delhi Daredevils vs Sunrisers Hyderabad  Feroz Shah Kotla, Delhi
Sat Apr 13  16:00 local | 10:30 GMT	15th IPL - Mumbai Indians vs Pune Warriors  Wankhede Stadium, Mumbai
Sat Apr 13  20:00 local | 14:30 GMT	16th IPL - Chennai Super Kings vs Royal Challengers Bangalore  MA Chidambaram Stadium - Chepauk, Chennai
Sun Apr 14  16:00 local | 10:30 GMT	17th IPL - Kolkata Knight Riders vs Sunrisers Hyderabad  Eden Gardens, Kolkata
Sun Apr 14  20:00 local | 14:30 GMT	18th IPL - Rajasthan Royals vs Kings XI Punjab  Sawai Mansingh Stadium, Jaipur
Mon Apr 15  20:00 local | 14:30 GMT	19th IPL - Chennai Super Kings vs Pune Warriors  MA Chidambaram Stadium - Chepauk, Chennai
Tue Apr 16  16:00 local | 10:30 GMT	20th IPL - Kings XI Punjab vs Kolkata Knight Riders  Punjab C.A. Stadium, Mohali
Tue Apr 16  20:00 local | 14:30 GMT	21st IPL - Royal Challengers Bangalore vs Delhi Daredevils  M.Chinnaswamy Stadium, Bangalore
Wed Apr 17  16:00 local | 10:30 GMT	22nd IPL - Pune Warriors vs Sunrisers Hyderabad  Subrata Roy Sahara Stadium, Pune
Wed Apr 17  20:00 local | 14:30 GMT	23rd IPL - Rajasthan Royals vs Mumbai Indians  Sawai Mansingh Stadium, Jaipur
Thu Apr 18  20:00 local | 14:30 GMT	24th IPL - Delhi Daredevils vs Chennai Super Kings  Feroz Shah Kotla, Delhi
Fri Apr 19  20:00 local | 14:30 GMT	25th IPL - Sunrisers Hyderabad vs Kings XI Punjab  Rajiv Gandhi Int. Stadium, Hyderabad
Sat Apr 20  16:00 local | 10:30 GMT	26th IPL - Kolkata Knight Riders vs Chennai Super Kings  Eden Gardens, Kolkata
Sat Apr 20  20:00 local | 14:30 GMT	27th IPL - Royal Challengers Bangalore vs Rajasthan Royals  M.Chinnaswamy Stadium, Bangalore
Sun Apr 21  16:00 local | 10:30 GMT	28th IPL - Delhi Daredevils vs Mumbai Indians  Feroz Shah Kotla, Delhi
Sun Apr 21  20:00 local | 14:30 GMT	29th IPL - Kings XI Punjab vs Pune Warriors  Punjab C.A. Stadium, Mohali
Mon Apr 22  20:00 local | 14:30 GMT	30th IPL - Chennai Super Kings vs Rajasthan Royals  MA Chidambaram Stadium - Chepauk, Chennai
Tue Apr 23  16:00 local | 10:30 GMT	31st IPL - Royal Challengers Bangalore vs Pune Warriors  M.Chinnaswamy Stadium, Bangalore
Tue Apr 23  20:00 local | 14:30 GMT	32nd IPL - Delhi Daredevils vs Kings XI Punjab  Feroz Shah Kotla, Delhi
Wed Apr 24  20:00 local | 14:30 GMT	33rd IPL - Kolkata Knight Riders vs Mumbai Indians  Eden Gardens, Kolkata
Thu Apr 25  20:00 local | 14:30 GMT	34th IPL - Chennai Super Kings vs Sunrisers Hyderabad  MA Chidambaram Stadium - Chepauk, Chennai
Fri Apr 26  20:00 local | 14:30 GMT	35th IPL - Kolkata Knight Riders vs Kings XI Punjab  Eden Gardens, Kolkata
Sat Apr 27  16:00 local | 10:30 GMT	36th IPL - Rajasthan Royals vs Sunrisers Hyderabad  Sawai Mansingh Stadium, Jaipur
Sat Apr 27  20:00 local | 14:30 GMT	37th IPL - Mumbai Indians vs Royal Challengers Bangalore  Wankhede Stadium, Mumbai
Sun Apr 28  16:00 local | 10:30 GMT	38th IPL - Chennai Super Kings vs Kolkata Knight Riders  MA Chidambaram Stadium - Chepauk, Chennai
Sun Apr 28  20:00 local | 14:30 GMT	39th IPL - Delhi Daredevils vs Pune Warriors  International Cricket Stadium, Raipur
Mon Apr 29  16:00 local | 10:30 GMT	40th IPL - Rajasthan Royals vs Royal Challengers Bangalore  Sawai Mansingh Stadium, Jaipur
Mon Apr 29  20:00 local | 14:30 GMT	41st IPL - Mumbai Indians vs Kings XI Punjab  Wankhede Stadium, Mumbai
Tue Apr 30  20:00 local | 14:30 GMT	42nd IPL - Pune Warriors vs Chennai Super Kings  Subrata Roy Sahara Stadium, Pune
Wed May 1  16:00 local | 10:30 GMT	43rd IPL - Sunrisers Hyderabad vs Mumbai Indians  Rajiv Gandhi Int. Stadium, Hyderabad
Wed May 1  20:00 local | 14:30 GMT	44th IPL - Delhi Daredevils vs Kolkata Knight Riders  International Cricket Stadium, Raipur
Thu May 2  16:00 local | 10:30 GMT	45th IPL - Chennai Super Kings vs Kings XI Punjab  MA Chidambaram Stadium - Chepauk, Chennai
Thu May 2  20:00 local | 14:30 GMT	46th IPL - Pune Warriors vs Royal Challengers Bangalore  Subrata Roy Sahara Stadium, Pune
Fri May 3  20:00 local | 14:30 GMT	47th IPL - Kolkata Knight Riders vs Rajasthan Royals  Eden Gardens, Kolkata
Sat May 4  20:00 local | 14:30 GMT	48th IPL - Sunrisers Hyderabad vs Delhi Daredevils  Rajiv Gandhi Int. Stadium, Hyderabad
Sun May 5  16:00 local | 10:30 GMT	49th IPL - Mumbai Indians vs Chennai Super Kings  Wankhede Stadium, Mumbai
Sun May 5  20:00 local | 14:30 GMT	50th IPL - Rajasthan Royals vs Pune Warriors  Sawai Mansingh Stadium, Jaipur
Mon May 6  20:00 local | 14:30 GMT	51st IPL - Kings XI Punjab vs Royal Challengers Bangalore  Punjab C.A. Stadium, Mohali
Tue May 7  16:00 local | 10:30 GMT	52nd IPL - Rajasthan Royals vs Delhi Daredevils  Sawai Mansingh Stadium, Jaipur
Tue May 7  20:00 local | 14:30 GMT	53rd IPL - Mumbai Indians vs Kolkata Knight Riders  Wankhede Stadium, Mumbai
Wed May 8  20:00 local | 14:30 GMT	54th IPL - Sunrisers Hyderabad vs Chennai Super Kings  Rajiv Gandhi Int. Stadium, Hyderabad
Thu May 9  16:00 local | 10:30 GMT	55th IPL - Kings XI Punjab vs Rajasthan Royals  Punjab C.A. Stadium, Mohali
Thu May 9  20:00 local | 14:30 GMT	56th IPL - Pune Warriors vs Kolkata Knight Riders  Subrata Roy Sahara Stadium, Pune
Fri May 10  20:00 local | 14:30 GMT	57th IPL - Delhi Daredevils vs Royal Challengers Bangalore  Feroz Shah Kotla, Delhi
Sat May 11  16:00 local | 10:30 GMT	58th IPL - Pune Warriors vs Mumbai Indians  Subrata Roy Sahara Stadium, Pune
Sat May 11  20:00 local | 14:30 GMT	59th IPL - Kings XI Punjab vs Sunrisers Hyderabad  Punjab C.A. Stadium, Mohali
Sun May 12  16:00 local | 10:30 GMT	60th IPL - Kolkata Knight Riders vs Royal Challengers Bangalore  JSCA International Cricket Stadium, Ranchi
Sun May 12  20:00 local | 14:30 GMT	61st IPL - Rajasthan Royals vs Chennai Super Kings  Sawai Mansingh Stadium, Jaipur
Mon May 13  20:00 local | 14:30 GMT	62nd IPL - Mumbai Indians vs Sunrisers Hyderabad  Wankhede Stadium, Mumbai
Tue May 14  16:00 local | 10:30 GMT	63rd IPL - Royal Challengers Bangalore vs Kings XI Punjab  M.Chinnaswamy Stadium, Bangalore
Tue May 14  20:00 local | 14:30 GMT	64th IPL - Chennai Super Kings vs Delhi Daredevils  MA Chidambaram Stadium - Chepauk, Chennai
Wed May 15  16:00 local | 10:30 GMT	65th IPL - Kolkata Knight Riders vs Pune Warriors  JSCA International Cricket Stadium, Ranchi
Wed May 15  20:00 local | 14:30 GMT	66th IPL - Mumbai Indians vs Rajasthan Royals  Wankhede Stadium, Mumbai
Thu May 16  20:00 local | 14:30 GMT	67th IPL - Kings XI Punjab vs Delhi Daredevils  HPCA Stadium, Dharmasala
Fri May 17  20:00 local | 14:30 GMT	68th IPL - Sunrisers Hyderabad vs Rajasthan Royals  Rajiv Gandhi Int. Stadium, Hyderabad
Sat May 18  16:00 local | 10:30 GMT	69th IPL - Kings XI Punjab vs Mumbai Indians  HPCA Stadium, Dharmasala
Sat May 18  20:00 local | 14:30 GMT	70th IPL - Royal Challengers Bangalore vs Chennai Super Kings  M.Chinnaswamy Stadium, Bangalore
Sun May 19  16:00 local | 10:30 GMT	71st IPL - Pune Warriors vs Delhi Daredevils  Subrata Roy Sahara Stadium, Pune
Sun May 19  20:00 local | 14:30 GMT	72nd IPL - Sunrisers Hyderabad vs Kolkata Knight Riders  Rajiv Gandhi Int. Stadium, Hyderabad
Tue May 21  20:00 local | 14:30 GMT	Qualifier 1 IPL - TBC vs TBC (1st Placed Team vs 2nd Placed Team)  MA Chidambaram Stadium - Chepauk, Chennai
Wed May 22  20:00 local | 14:30 GMT	Eliminator IPL - TBC vs TBC (3rd Placed Team vs 4th Placed Team)  MA Chidambaram Stadium - Chepauk, Chennai
Fri May 24  20:00 local | 14:30 GMT	Qualifier 2 IPL - TBC vs TBC (Winner of Eliminator vs Loser of Qualifer 1)  Eden Gardens, Kolkata
Sun May 26  20:00 local | 14:30 GMT	Final IPL - TBC vs TBC (Winner of Q1 vs Winner of Q2)  Eden Gardens, Kolkata