• Games Testing Solutions

    We offer Game QA Testing services on most platforms which include iPhone, iPad, Android based Tablets/Mobile devices, PC, MAC etc

  • Automation Testing

    Automation testing is primarily used for performing regression testing of a product. Regression testing requires execution of Test Cases with every build.

  • Affordable Testing Solutions

    Precise Testing Solution are fully committed to deliver organize, systematic and best-in-class quality assurance, adopting latest authentic mythologies of industry..

Tuesday, 11 October 2011

Agile software development methodology with scrum

Agile software development methodology with scrum

Agile software development is a methodology for undertaking software development projects in which incremental functionality is released in smaller cycles, and work is performed in a highly collaborative manner by self-organizing teams that embrace and adapt changes to ensure that customer's needs are truly met. In Agile Software Development the final product is truly what customers requested. The idea behind the Agile approach is that instead of building a release that is huge in functionality (and often late to market), an organization would adapt to dynamic changing conditions by breaking a release into smaller shorter cycles of 1 to 6 weeks. Each cycle is called an iteration, or sprint, and it’s almost like a miniature software project of its own, because it includes all of the tasks necessary to release the incremental new functionality. Agile methodology emphasizes real-time communication, preferably face-to-face, versus written documents and rigid processes. In addition, one of the most broadly applicable techniques introduced by the agile processes is to express product requirements in the form of user stories. Each user story has various fields including an "actor", a "goal" or task that they need to perform, an explanation
Most agile teams include all the people necessary to release software. At a minimum, this includes programmers and the group or team they are developing the application for, often referred to as their "customers" (customers are the people who define the product; they may be product managers, business analysts, or actual customers). Typically an agile team will also include a ScrumMaster, testers, interaction designers, technical writers, and managers.
What is scrum ? Scrum is really a project management methodology to facilitate agile software development, and enable the creation of self-organizing agile teams. A ScrumMaster is like a traditional project manager in the sense that he/she oversees the centralization of team communication, requirements, schedules and progress. But it is also very different because his/her main responsibility is to facilitate team communications and provide guidance and coaching, while removing impediments to the ability of the team to deliver its goals. Unlike a traditional project manager, the ScrumMaster doesn’t direct the team, because an agile team is based on the philosophy that a team member is committed to the other team members, not to a management authority.
Phases of an Agile Development Project using Scrum
Agile can be customized to fit each corporation in terms of size, iteration time, experience, etc, but typically an agile project will have these phases and milestones.
  1. Kickoff meeting. Although this may seem routine for any project, with an agile development project this is a key element for getting the project launched. The goal of this meeting is to get everybody on the team together to review the product backlog (which is the master list of all requirements desired in the product that the product owner has drafted in the form of user stories), as well as the user personas (or the profile of each type of product user). In my opinion, this is a nicer and clearer way to introduce product requirements, because you really have more visibility into who is using the product, what are they trying to achieve and why, right from the beginning.
A kickoff meeting usually lasts at least half a day with everybody together going over a “story writing workshop” -- in which stories are selected and then decomposed into programmable tasks and written in a white board together along with the time estimates for completion. If you have never seen a product backlog, you can check few samples here in QAZone . Sometime real customers are invited to the kickoff meeting as well to review and clarify the product backlog with the agile team.
  1. The next step in the sprint/iteration planning, in which the team collectively decides the sprint goal and sprint backlog (list of prioritized work to be done for that particular sprint). While the team is collectively creating the sprint backlog, stories need to be broken into either sub-stories or smaller tasks. During this collective team exercise you can really see the differences in project management (at least if you have a more rigid and formal waterfall like type of background), because there is no management authority that assigns tasks to team members. On an agile team all the members jointly associate level of difficulty to specific tasks, they can remove or add additional stories and/or tasks, and tasks are distributed among the team on a per volunteers basis. Unlike a traditional project manager function, the ScrumMaster role in this meeting is to maintain the backlog list in the meeting based on team feedback and consensus, make sure that nobody is volunteering for too many tasks to the point of overload, and facilitate the process of building personal commitment to the team.
  1. Now that the Sprint planning is ready in the form of sprint backlog –which is dynamic and not set in stone, in fact it is very likely that it will adapt and change based on new stories, new tasks and/or impediments found throughout the iteration– scrum meetings will be set at the same time and in the same place on a daily basis. If you have never attended a scrum meeting, these meetings are very dynamic in nature and fast, never more than 30 minutes, and ideally 10-15 minutes. The objective is to go around so each team member can answer 3 questions: what have I accomplished since the last meeting (developed, tested, written, etc), what will I be working on next, and what are the problems, if any, preventing me from accomplishing my goals. These meetings are very important to make sure that the team moves towards achieving their sprint goal, or adapts/evolves and changes priorities and tasks as needed if new stories, impediments or new scenarios are encountered.
  1. At the end of the sprint or iteration, usually a final acceptance meeting takes place, which is typically done by presenting what the team has accomplished, and by delivering a demo to the customer or to a larger audience.
  2. At the end of an iteration there is also a sprint retro meeting, similar to a postmortem meeting at the end of other traditional projects, so the team gets together to evaluate what worked well, and what needs to be improved during their next iteration.
Top 3 things a QA professional should expect when an organization adopts Agile/Scrum development techniques
Agile and Scrum are really changing the way testing is perceived throughout the project. Testing is not a phase at the end; it really is integrated throughout the entire iteration cycle, and it goes hand in hand with programming tasks. In my experience, when comparing a testing role performed within an agile project, or when using more rigid and formal approaches, I have found that with agile methodologies there is:
  1. Better communication and more collaboration among QA & development folks
Gone are the days of "give me requirements" and "I will give you bugs and reports back"...QA folks are involved in the project from the start–along with their development counterparts–and they have access to the same information about product requirements and customer needs at the same time. This participation from the onset, combined with the fact that development and QA are part now of the same agile team, that they get together on a daily basis, and that they have full visibility into the tasks that each other is performing towards the overall success of the sprint, means better and more frequent communication among themselves. In addition, because the entire team meets every day (development, QA, product management, etc) there are more opportunities for collaboration and more view points towards performing a particular task. Also the traditional "rivalry" that you may find among QA and development is eliminated because there is a single agile team now working to achieve a common goal.
  1. A new "peer to peer" relationship between development and QA personnel
You should be prepared to "speak up" much more. Agile methodologies are all about building self-organized teams, and the voice of a QA engineer/tester carries the same weight than a developer. Think about it. In the daily scrum meeting each team member gets asked about their accomplishments (testing, developing, writing product documentation, etc), future plans, and obstacles, treating all of the members as equal partners. On an agile team the question of "how are we going to test it", is as important as "how are going to build it". In addition, because testers tend to be exceptionally good at clarifying requirements and identifying alternative scenarios, (especially when they have full visibility into product requirements and customer needs), they provide valuable input on design and architectural decisions throughout the project, right from the beginning. And these contributions translate into more respect and appreciation from their development counterparts.
  1. Looking for ways to optimize testing efforts will be a "must" You really need to think about automation, and planning and performing your testing efforts very efficiently. With shorter development cycles of typically no more than 6 weeks, and with builds being released all the time, testing efforts really need to be optimized as much as possible, because there is not separate test phase as such. One of the ways to achieve this is by leveraging both Exploratory Testing and Automated Testing throughout the project. Exploratory testing will come very handy when looking for bugs, opportunities to improve, and missing features. So you should plan on "exploring" the product at the beginning of each new sprint, or any time that there is a change done to a product feature within the sprint cycle. Similarly, you will need to plan and build your scripts to perform automated functional and regression testing within the sprint, because there is not enough time for performing thorough manual testing. One of the things to remember is that there are no really lengthy requirement document or specifications–other that the stories encapsulated on the backlog files–so the only way to make sure that each feature is fully developed, tested, and accepted by the product owner before counting it as "DONE!", is by using the sprint backlog as your own test plan (or writing a test case or script for every feature). Some teams are treating test case scenarios as entries that need to be added to the product/sprint backlog files for planning and tracking purposes. Another factor to consider is that development is much more heavily engaged in testing, so you should leverage this, and work very closely with them to plan and build more automated scripts that cover realistic scopes.
For More Detail Please Refer this link

SAP Window Application Testing Through QTP

About Setting Up Your SAP Windows Environment

Quick Test Professional's support for SAP graphical user interface (GUI) for Window’s versions 6.20, 6.40 and 7.10 is based on the SAP GUI writing API which is disabled by default.

To test your SAP GUI for Windows application using the Quick Test Professional add INS for SAP results, you compulsion that confirm:

    • The SAP graphical user interface (GUI) writing option is installed.
    • Your server and client have the proper package and patch versions installed.
    • Your server supports the Scripting API.
    • The Scripting API is enabled on both the server and clients.
    • Your client is configured to use the Dialog display mode for F4 Help screens and that it is not set to use a Low speed connection.
    • The F1 and F4 Help display setting is configured correctly, to support testing the use of the F1 and F4 Help screens in your SAP graphical user interface (GUI) application.

Installing SAP GUI Scripting Support

When you install your SAP graphical user interface (GUI) for window’s application, you must select s SAP graphical user interface (GUI) writing installation option. 

If you did not select this option when you installed the SAP graphical user interface (GUI) for Window’s application, it is essential that you reinstall it and select this option previous setting the other configuration alternatives described in this block.
Note: SAP supplies the range of security techniques that allow the administrator to limit the use of SAP graphical user interface (GUI) Scripting through system, by through group, via user, & through functionality. To test SAP (GUI) for Window’s apps, you must ensure that these security techniques are not started for the application you are testing. For various data on the various security options, see the online SAP GUI Scripting Security Guide at the SAP Service Marketplace.

Checking Package and Patch Versions Installed on the SAP Application Server

To use the Quick Test Professional (QTP) Add INS for SAP resolutions, you must be confirmed that you hold the correct support package or kernel patch steps for your software part released. The following tables show the minimum requirement of variants & phases. You must get these versions and levels or highly: SCRP Kernel Patch Level

Software Component


Support Package

Kernel Patch Level




Kernel 3.1I level 650




Kernel 4.0B level 903




Kernel 4.5B level 753




Kernel 4.6D level 948




Kernel 4.6D level 948




Kernel 4.6D level 948




Kernel 6.10 level 360
      If the correct package is installing of a green lighted icon is shows in the status part.
      If you don’t have the needed packages installed, download & installed it.
      For more data on downloading & installed the required package, see SAP open source software (OSS) note #480149.

  • Log on to your SAP server.
  • Select System > status. The system: status’s dialog box operating system (os) is opened.

    1. In the Kernel’s data part, checks the value of Sup. Pkg. level.
    If the phase is lower than the needed phase for the SAP is release than you are using.

For various data on downloading and installing the required kernel patch level, see SAP OSS note #480149.

Checking the Patch Version Installed on your SAP GUI for Windows Application

If you need to test your SAP graphical user interface (GUI) for Window’s application with the Quick Test Professional add-ins for SAP Solutions, make confident that the minimum required patch level is installed. For the more data on required patch levels, see the HP Quick Test Professional (QTP) ware availability Matrix, present from documentation library home page (DLHP) and the root folder of the Quick Test Professional (QTP) DVD.

Note: : If the minimum required patch level is not installed, an error message is displays when you trying to record your SAP Graphical User interface (GUI) for Window’s application.
To check the patch level on your SAP Graphical User interface (GUI) for Window’s application:

  • Open SAP Login dialog box & click on that button present on the left hand side the SAP Login dialog box title bar. Then select About the SAP Login from menu.

    Enabling Scripting

    Quick Test (QT) communicates straightly with the SAP Graphical User Interface (GUI) Scripting API to record and executes your activity on SAP Window’s object. For example, Quick Test (QT) records level based straightly on the application Programming Interface (API) actions that are sent from clients to the SAP server. Therefore, to record & executes Quick Test tests & elements on your SAP Graphical User Interface (GUI) for Window’s application, you must enable the writing on both the server side & client side. For more data, look the following steps:

      • Enabling writing (Scripting) on the SAP Application (Server-Side)
      • Enabling writing (Scripting) on the SAP Application (Client-Side)

    • Enabling Scripting on the SAP Application (Server-Side)

      After you confirmed that you get the proper support package & kernel patch phases is installed, you just enable play scripts on your SAP application. By default, writing (scripting) is disabled.
      You must enable writing (scripting) through entering in the maintain profile parameter’s window with administrative accessibility & setting the sap GUI and user writing profile parameter is TRUE on the applications server.
      To enable scripting for every user, fix this parameter on each applications server. To enable scripting for a particular group of users, fix the parameter only on application’s server with the appropriate accession restriction of settings.
      Note: If you connect to the server on which writing is out of action, an error message shows when you trying to record on your SAP Graphical User Interface (GUI) for Window’s application.
      To changes the profile parameter:
        1. Enter nrz11 in OKCode and edit box to open for transaction rz11.
        2. In the Param. Name of box is Maintains the Profile Parameters windows, and enter sap GUI /user scripting and click the Display button.

    1. Enter TRUE in the New value box and click on the Save button. .
    2. Note: You compulsions enter the TRUE in all caps locks words. Entering true and true has no effected.
      When you to save the changes and the window closed & the value of the parameter is shows as the TRUE. Even so, this change takes effects only when you login system. Hence, before starting work with Quick Test Professional (QTP) Add INS for SAP results, you compulsory log out & login again. You might also be needed to re-start the SAP Service from SAP Console.

      If you find that; yet after re-starting the SAP Services from SAP Console & logging again to the customer, your variation is to the Profile Val parameter was non saved, you might be have an out dated kernel variant. In this situation, either again start the application server and download or import the needed the kernel patch, as defined below.


    Kernel Version

    Patch Level





    all versions

    all levels


    all versions

    all levels


    all versions

    all levels

    For more data & download guidelines, see SAP OSS note #480149

    Enabling Scripting on the SAP Application (Client-Side)

    To test SAP Graphical user Interface (GUI) for Window’s applications with Quick Test Professional, you must confirm that scripting is enabled on the SAP GUI for Windows client.
    It is also recommended to disable warning messages in the SAP GUI for Windows environment when working with Quick Test Professional.
    To ensure that scripting is enabled on the SAP GUI for Windows client:

      1. Log on to your SAP server.
      2. Click the Customize Local Layout  SAP toolbar button and then select Options. The Options dialog box opens.
      3. Click the Scripting tab.

    Enabling writing(Scripting) on the SAP Application (Client-Side)

    To test Graphical user Interface (GUI) for Window’s applications with Quick Test Professional, you must confirm that scripting is enabled on the SAP GUI for Windows client.
    It is also recommended to disable warning messages in the SAP GUI for Windows environment when working with Quick Test Professional.
    To ensure that scripting is enabled on the SAP GUI for Windows client:

      1. Log on to your SAP server.
      2. Click the Customize Local Layout  SAP toolbar button and then select Options. The Options dialog box opens.
      3. Click the Scripting tab.

    Eliminating Warning Messages

    By default, you regularly receive two warning messages when using Quick Test Professional with an SAP Graphical User interface (GUI) for Window’s application:

    • When Quick Test Professional connected to the writing (scripting) Application Programming Interface (API), the following warning messages is exposed: A play script is trying to attached with the GUI.

    • When Quick Test Professional opens a newer connection using the writing the Application Programming Interface (API), the following warning message is seemed: A play script is opens a connection with the system <system name>.

    It is recommended to disable these popup messages in the SAP Graphical User Interface (GUI) for Window’s application when working to Quick Test Professional.
    To eliminate the display of warning messages:

    1. Log on to your SAP server.

    2. Click the Customize Local Layout SAP toolbar button and then select Options. The Options dialog box opens.

    3. Click the Scripting tab.
    4. Clear the Notify When a Script Attaches to a Running GUI and Notify When a Script Opens a Connection check boxes and click OK.  
    5. Setting F4 Help to Use Dialog Display Mode

      When the SAP GUI for Windows application uses the SAP GUI Scripting API (Enable Scripting option), it cannot load the F4 Help screens in Control mode. Therefore, you must ensure that your customers are fixing to load F4 Help displays in Dialog manner.
      Note: This is per user setting. You must set these alternatives on all customers that you want to test using the Quick Test Professional add INS for SAP results. instead, of the system default can be changed by the SAP system administrator.
      To set F4 Help to use Dialog mode:

    6. Log on to your SAP server.

    7. Select Help > Settings from the SAP menu bar. Your Person Settings dialog box opens.

    8. Click the F4 Help tab.

      Checking the Connection Speed on the SAP Server

      When you log on to SAP using the down speed connection alternatives to communicate with the server, the SAP server does not send sufficient information for Quick Test to properly record and run tests. (Quick Test shows an error messages if the down speed connection alternatives is chosen.) Therefore, confirmed that this alternative is not chosen for the server to which you are connecting previous recording & executing Quick Test tests.

      For more information, see SAP OSS note #587202.
      Note: Depending on the SAP GUI for Windows version you are working with, the dialog boxes shown in this section may or may not appear the same as those on your screen. However the instructions in this section are the same for all supported SAP GUI for Windows versions.
      To check the connection speed setting on your SAP GUI for Windows client:

      1. Open the SAP Logon dialog box and select the server to which you want to connect.
      2. According to the version you are using, either click the Properties button or right-click a server and select Properties. The Properties dialog box for the selected server opens.

    9. In the Connection speed section, confirm that the Low speed connection check box is cleared.

    10. Repeat steps 1 to 4 for each server you want to use in conjunction with QuickTest.

    Bookmark Us

    Delicious Digg Facebook Favorites More Stumbleupon Twitter