Tuesday, 27 September 2016

Bug Management and Test Management Steps

Mantis Steps:
1. We can report a bug
2. We can set the priority and Serverity of the bug
3. We can assign bug to the developer
4. We can track complete bug activity
5. We can set relationship of the bugs like parent and child
6. We can define status to the bug
7. We can generate HTML report of the bugs.
TestLink Steps:
1. Create a new Project- Done
2. Create a new test plan- Done
3. Create Release/Build under specific test plan- Done
4. Create test suite- Done
5. Create Test Cases under specific  test suite- Done
6. Link Test cases to the release/build- done
7. Create users(Testers)- Done
9. Execute Test cases- Done
10. Check Reports
Manual Test Case Steps:
Heading:
 Client Name,Project Name, Version,Module Name,Browser,Date, Platform,
Details:
Id,Author, Category, Priority, Testing Type, Test Scenario and Test Steps, User Role,
Test Data, Expected Results, Test End State, Tester,Version, Date, Platform, Actual Result,
Status, Remark


Thursday, 22 September 2016

Manual Testing



1.      Error: An Error is a Mistake.
2.      Bug: During Testing of Application When Testing Team Found Actual Result do not match with the expected result.
3.      Defect: Once Project or Product is Release, then during working by Client or their end user if something wrong identified, it is called defect.
4.      Failure: Once Project or Product is Release and more defects are identified by end users then project is known as failure.
5.      Software Testing: Software Testing is process of executing an application with the intent of finding an error.
6.      CMMI Levels:
i)                    Initial
ii)                  Repeatable
iii)                Defined
iv)                Managed
v)                  Optimized
7.      SDLC : Software Development Life Cycle:
i)                    Requirement Gathering:
-          BD Gets the Projects to the company
-          BD Pass the call to BA
-          BA gathers details of requirement from clients.
-          Requirement can be either functional or non- functional.
-          Functional requirement means core functionality of an application.
-          Nonfunctional requirement means overall behavior of application like performance, usability, security, compatibility.
-          BA Prepares BRD.
-          BA sends the document to development team as well as test.
ii)                  Analysis and Planning
-          Define Scope of the project.
-          Feasibility study of the requirement
-          Analyzing risk factors.
-          Effort estimation
-          Cost estimation
-          Deciding programing language of application
-          Preparing gantt chart.
-          Completing the requirement analysis
-          Delimiting the problem domain
iii)                Design
-          Determining which system component will cover which requirement in the system specification.
-          How these system component will work together.
-          Prepares low level design level designs known as prototype or blue print.
-          Prepare high level designs known as DFD, Flowchart, database architecture, algorithms.
-          Description of the Logical data model.
iv)                Development
-          Refining the algorithms for the individual components.
-          Transferring the algorithms into programing languages.
-          Translating the logical data model into a physical one.
-          Compiling and checking the syntactical correctness of the code.
-          Development team starts writing code according to the design prepared by designing team.
v)                  Testing
-          Testing the manual effects of system components under conditions close to reality.
-          Detecting as many errors as possible in the software system.
-          Assuring that the system implementation fulfills the system specification.
-          Perform function and non-function testing against requirement.
vi)                Deployment
-          Product move to production environment for acceptance testing
-          Mainly done by client and their end user
-          Main goal is to check the business flow of the application
-          Correcting errors that are detected during actual operation
vii)              Release
-          Application is published for their end user general public
-          Code is being sent to the website owner.
-          Handover of different document or deliverables to the company.

8.      STLC Life Cycle(Software Testing Life Cycle)
i)                    Requirement Analysis
-          Analysis client requirement in details
-          Deciding testing priorities
-          Checking up automation feasibilities
ii)                  Test Planning
-          Preparation of Test Plan
-          Selection of Testing tools
-          Test effort estimation
-          Resource planning and determining role and responsibilities
-          Training requirement
-          Staffing requirement
-          Define scope of approach
-          Test deliverables: STP (Software Test Plan Document), Gantt chart of Testing.
iii)                Test Case Preparation & Development
-          Create test data for the test cases
-          Development of test cases
-          Approval of test case document
-          Development of automation testing scripts
-          Test deliverables: Preparation Test data, Test case , Test Script Development
iv)                Test Environment Setup
-          Setting up all hardware component
-          Installation of all required software
-          Installation and configuration of testing tools
-          Copying required document
v)                  Test Execution & Bug Reporting
-          Execution of test case
-          Bug reporting to bug tracking system
-          Retesting of the bug after fixes
-          Mapping of bugs with the test cases
-          Test deliverables:  Bug Reporting from bug management tool, updating test case document
vi)                Test Cycle Closure:
-          Submitting STR(Software Test result)
-          Submitting test summary report, test plan document,test case/script etc…
-          Sharing experiences with the team.

-