Wednesday, 22 February 2017

With Sprinter Tester, can:

o    Create and run macros to allow Sprinter to perform a set of actions on the application.

o    Sprinter can automatically enter data into fields in the application for you.

o    The data is automatically matched to your application's fields.

o    Mirroring can replicate user actions on another computer with different configurations (operating system, browser).

o    Run exploratory tests with no predefined steps.

o    Annotation Tools are included for measuring and comparing user interface elements.

o    A tester can also include annotated screen captures in the Actual Result of a step Submit defects to HP ALM.

o    Submit an HP ALM defect directly from within Sprinter.

o    Smart Defects create a defect scenario by automatically generating a text description of all the user actions or steps in the test.

o    Run HP ALM manual tests and Business Process tests with a new step display.

o    User-friendly display. Steps are presented in a clear, organized, and user-friendly design, making it easier to view step information, navigate steps, and modify step information Edit actual values of parameters during a test run.

o    Actual value including screen captures. Attach a plain or annotated screen capture of your application to the step's actual value.

o    Create a Defect Reminder to submit a defect at the end of run, enabling tester to keep testing without
o    interrupting the flow of test run.

o    Sprinter includes a Storyboard that displays an overall summary of each action tester performed in during test.

o   It will list screen capture of the actions, any defects that are reported, defect reminders and comments added to run.

Friday, 17 February 2017

Employ the tips given below to craft a powerful resume.

·         If you have worked in different companies and in different positions and domains, you can use the functional format to highlight different roles and functions.
·         Provide more accomplishments than responsibilities.
·         List out your primary responsibilities first followed by secondary responsibilities. Do not include day-to-day mundane tasks or work that you take up on a daily basis.
·         Keep your personal details to a minimum by excluding your family's history and their details.
·         Your resume should not be loaded with too much content nor should it seem insufficient with too less.
·         An average of 3 pages would be sufficient for candidates in the middle management level.
·         Do not mention salary details, expected salary or perks in the resume.
·         It is better to discuss these details during the interview.
·         If you are a software professional who has worked in different projects, pick out 3 - 4 projects that you think is important and include only these in your resume.
·         Images, logos, and flowcharts should not be used in a career document, so avoid inserting them in your resume.
·         Do not italicize, highlight or use color fonts in your resume.
·         List out your responsibilities and achievements in bullet points thereby avoiding the use of paragraphs

Thursday, 16 February 2017

What will be done after a defect/bug is found in project/application?

The bug has to be communicated and assigned to developers which will fix it.
when the matter is resolved, fixes ought to be re-tested, and determinations created concerning needs for regression testing to examine that fixes did not produce issues elsewhere.
If a problem-tracking system is in repository, it ought to encapsulate these processes.
A range of business problem-tracking/management software system tools square measure offered (see the 'Tools' section for net resources with listings of such tools).
the subsequent square measure things to contemplate within the chase process:
•         Complete info specified developers will perceive the bug, get a plan of its severity, and reproduce it if necessary.
•         Bug symbol (number, ID, etc.)
•         Current bug standing (e.g., 'Released for Retest', 'New', etc.)
•         The application name or symbol and version
•         The perform, module, feature, object, screen, etc. wherever the bug occurred
•         Environment specifics, system, platform, relevant hardware specifics
•         Test case name/number/identifier
•         One-line bug description
•         Full bug description
•         Description of steps required to breed the bug if not coated by an action or if the developer does not have quick access to the check case/test script/test tool
•         Names and/or descriptions of file/data/messages/etc. utilized in check
•         File excerpts/error messages/log file excerpts/screenshots/test tool logs that may be useful to find the explanation for the matter
•         Severity estimate (a 5-level vary like 1-5 or 'critical'-to-'low' is common)
•         Was the bug reproducible?
•         Tester name
•         Test date
•         Bug reportage date
•         Name of developer/group/organization the matter is assigned to
•         Description of downside cause
•         Description of fix
•         Code section/file/module/class/method that was fixed
•         Date of fix
•         Application version that contains the fix
•         Tester responsible for retest
•         Retest date
•         Retest results
•         Regression testing requirements
•         Tester responsible for regression tests
•         Regression testing results
•         A reporting or tracking process should enable notification of appropriate personnel at various stages.
•         For instance, testers need to know when retesting is needed, developers need to know when bugs are found and how to get the needed information, and reporting/summary capabilities are needed for managers.

Wednesday, 15 February 2017

Software Quality Standards

  • Software Quality Standards
    • Quality standards are a way to ensure that the product being developed is a well-engineered product.
    • ISO: International Organization for Standards
    • CMMI: Capability Maturity Model Integration
    • IEEE: Institute of Electrical and Electronics Engineers
    • ANSI: American National Standards Institute
    • ASQ: American Society for Quality
    • SEI: Software Engineering Institute
  • Why software Quality Standards are required?
    • To ensure the quality
    • To have the transparency
    • To have the discipline
    • To satisfy the customer
    • Key Selling Point (KSP)
    • Reducing the Rework
  • Quality Standards – ISO
    • ISO 9000 - General guidelines for procedures and processes
    • ISO 9001 - Covers Documentation, Design, Development, Production, Testing, Installation, Servicing and Marketing etc.
    • ISO 9002 - Except Design all other aspects
    • ISO 9003 - Only for Inspection and Testing
    • A companies’ quality system and operations are scrutinized by third-party auditors for compliance with the standard and for effective operation
    • Upon successful registration, a company is issued a certificate from a registration body represented by auditors
    • Semi-Annual surveillance audits ensure continued compliance with the standard
    • For a quality system to be ISO compliant, these processes must address the areas identified in the standard and must be documented and practiced as described
    • ISO 9001 is most comprehensive and this is the one most often used by software development organizations
    • As ISO 9001 standard is applicable to all engineering disciplines, a special set of ISO guidelines (ISO 9000-3) have been developed to help interpret the standard for use in the software process
  • Quality Standards – CMMI
    • Capability Maturity Model Integration
    • It is developed by the SEI. It is a model of 5 levels of organizational maturity that determine effectiveness in delivering quality software.
    • Organizations can receive CMM ratings by undergoing assessments by qualified auditors
    • There are 5 maturity levels, each level is composed of  “Key Process Areas”
    • A Key Process Area (KPA) is a cluster of related activities that when performed together collectively achieve a set of goals important for establishing process capability at that maturity level
    • CMMI Level 1:
    • Initial, the software process is characterized as ad hoc. Few processes are defined, and success depends on individual effort
    • CMM Level 2:
    • Basic Project Management to track cost, schedule, and functionality
  • This level involves five KPAs
    • Software Configuration Management
    • Quality Assurance
    • Subcontract Management
    • Project Tracking
    • Project Planning & Requirements
    • Management
    • CMMI Level 3:
    • Standard software development and maintenance processes are integrated throughout an organization
    • Software engineering process group is in place to oversee software process and training programs are used to ensure compliance. KPAs are...
  • Inter group co-ordination
    • Software Project Engineering
    • Integrated Software Management
    • Peer to Peer Reviews of Reports
    • Organization Process Definition
    • Organization Process Focus
  • CMMI Level 4:
    • Detailed measures of the software process and product quality are measured. This level has 2 KPA’s
    • Software Quality Management
    • Quantitative Process Management
  • CMMI Level 5:
    • Enable quality process improvement by quantitative feedback from the process and from testing innovative ideas and technologies. 3 KPAs at this level are:
    • Process Change Management
    • Technology Change Management
    • Defect Prevention

Tuesday, 14 February 2017

What steps are needed to develop and run application tests?

The following are the variety of the steps to consider:
·         Obtain requirements, functional mode, and internal design specifications and various necessary documents.
·         Obtain budget and schedule requirements.
·         Determine project-related personnel and their responsibilities, reporting wants, required standards, and processes (such as release procedures, change procedures, etc.)
·         Identify application's higher-risk aspects, set priorities, and determine scope and limitations of tests.
·         Determine test approaches and classifications - unit, integration, functional, system, load, usability tests, etc.
·         Determine test surroundings wants (hardware, software, communications, etc.)
·         Determine test were wants (record/playback tools, coverage analyzers, test trailing, problem/bug tracking, etc.)
·         Determine test input information wants
·         Identify tasks, those responsible for tasks, and labor requirements
·         Set schedule evaluations, timelines, milestones
·         Determine input equivalence classes, boundary value analyses, error classes
·         Prepare test set up document and have needed reviews/approvals
·         Write test cases
·         Have needed reviews/inspections/approvals of taking a look at cases
·         Prepare to take a glance at surroundings and test ware, obtain needed user manuals/reference documents/configuration guides/installation guides, set up test trailing processes, set up logging and archiving processes, set up or obtain take a glance at file
·         Acquire and install software releases
·         Perform tests
·         Estimate and report results Track problems/bugs and fixes
·         Retest as needed

·         Maintain and update test plans, test cases, test surroundings, and test were through life cycle

Sunday, 12 February 2017

Focus on the following areas for System Testing:

·         Authorization:  Whether user is valid or not to login to application
·         Access Control:  Whether a valid user have permission to access specific service
·         Audit Trail:  Maintains metadata about user operation in our application
·         Continuity of Processing: Inter-process communication
·         Correctness:  Meet client requirement in terms of functionality
·         Coupling:  Co-existence with other existence software to share resources
·         Ease of Use:  User Friendliness of the application visibility
·         Ease of Operator:  Installation, Un-installations, Dumping, Uploading, Downloading, etc.,
·         File Integrity:  Creation of backup
·         Reliability: Recover from abnormal state
·         Performance:  Speed of processing
·         Portable:  Run on different platforms
·         Service levels:  Order of functionalities

·         Maintainable: Whether our application build is long