Different Testing Aspects and Areas or Types of Testing

Following are the different aspects and areas or type of testing not only in mobile application testing:

Functionality

  • User Interaction Testing
  •  Transaction testing

Performance

  • UI responsiveness
  • Transaction completion time(s)
  • Peak load performance
  • Longevity

Network

  • Network type (Wi-Fi, 2G, 3G, 4G)
  • Impact of Connectivity Issues

Security

  • Data Retention on device
  • Transmission Security

Compatibility

  • Mobile Platform Compatibility (e.g. iOS 9.x, iOS 8.x, iOS 7.x, iOS 6,
    iOS 5.1.1, iOS 5.1.1)
  • Device Model Compatibility
  • Backward compatibility (with previous app version)

Conformance

  • Marketplace guidelines compliance (e.g. Apple App Store policies)
  • Enterprise policy compliance (e.g. prohibited content)

Usability

  • User Experience

Installation and Provisioning

  • Installation process
  • Un-installation process
  • User provisioning and de-provisioning.

App Store Review Guidelines

Appstore_2610363b

Following are some important guidelines that should be follow while App Store release:

Sl. No. Category/Type Description
1 Functionality Apps that crash will be rejected
2 Functionality Apps that exhibit bugs will be rejected
3 Functionality Apps that do not perform as advertised by the developer will be rejected
4 Functionality Apps that include undocumented or hidden features inconsistent with the description of the App will be rejected
5 Functionality Apps that use non-public APIs will be rejected
6 Functionality Apps that read or write data outside its designated container area will be rejected
7 Functionality Apps that download code in any way or form will be rejected
8 Functionality Apps that install or launch other executable code will be rejected
9 Functionality Apps that are “beta”, “demo”, “trial”, or “test” versions will be rejected
10 Functionality iPhone Apps must also run on iPad without modification, at iPhone resolution, and at 2X iPhone 3GS resolution
11 Functionality Apps that duplicate Apps already in the App Store may be rejected, particularly if there are many of them, such as fart, burp, flashlight, and Kama Sutra Apps
12 Functionality Apps that are not very useful, unique, are simply web sites bundled as Apps, or do not provide any lasting entertainment value may be rejected
13 Functionality Apps that are primarily marketing materials or advertisements will be rejected
14 Functionality Apps that are intended to provide trick or fake functionality that are not clearly marked as such will be rejected
15 Functionality Apps larger than 100MB in size will not download over cellular networks (this is automatically prohibited by the App Store)
16 Functionality Multitasking Apps may only use background services for their intended purposes: VoIP, audio playback, location, task completion, local notifications, etc.
17 Functionality Apps that browse the web must use the iOS WebKit framework and WebKit Javascript
18 Functionality Apps that encourage excessive consumption of alcohol or illegal substances, or encourage minors to consume alcohol or smoke cigarettes, will be rejected
19 Functionality Apps that provide incorrect diagnostic or other inaccurate device data will be rejected
20 Functionality Developers “spamming” the App Store with many versions of similar Apps will be removed from the iOS Developer Program
21 Functionality Apps that are simply a song or movie should be submitted to the iTunes store. Apps that are simply a book should be submitted to the iBooks Store
22 Functionality Apps that arbitrarily restrict which users may use the App, such as by location or carrier, may be rejected
23 Functionality Apps must follow the iOS Data Storage Guidelines or they will be rejected
24 Functionality Apps that are offered in Newsstand must comply with schedules 1, 2 and 3 of the Program License Agreement or they will be rejected
25 Functionality Apps that display Apps other than your own for purchase or promotion in a manner similar to or confusing with the App Store will be rejected, unless designed for a specific approved need (e.g. health management, aviation, accessibility, etc.) or which provide significant added value for a specific group of customers
26 Metadata (name, descriptions, ratings, rankings, etc.) Apps or metadata that mentions the name of any other mobile platform will be rejected
27 Metadata (name, descriptions, ratings, rankings, etc.) Apps with placeholder text will be rejected
28 Metadata (name, descriptions, ratings, rankings, etc.) Apps with names, descriptions, or screenshots not relevant to the App content and functionality will be rejected
29 Metadata (name, descriptions, ratings, rankings, etc.) App names in iTunes Connect and as displayed on a device should be similar, so as not to cause confusion
30 Metadata (name, descriptions, ratings, rankings, etc.) Small and large App icons should be similar, so as to not to cause confusion
31 Metadata (name, descriptions, ratings, rankings, etc.) Apps with App icons and screenshots that do not adhere to the 4+ age rating will be rejected
32 Metadata (name, descriptions, ratings, rankings, etc.) Apps with Category and Genre selections that are not appropriate for the App content will be rejected
33 Metadata (name, descriptions, ratings, rankings, etc.) Developers are responsible for assigning appropriate ratings to their Apps. Inappropriate ratings may be changed/deleted by Apple
34 Metadata (name, descriptions, ratings, rankings, etc.) Developers are responsible for assigning appropriate keywords for their Apps. Inappropriate keywords may be changed/deleted by Apple
35 Metadata (name, descriptions, ratings, rankings, etc.) Developers who attempt to manipulate or cheat the user reviews or chart ranking in the App Store with fake or paid reviews, or any other inappropriate methods will be removed from the iOS Developer Program
36 Metadata (name, descriptions, ratings, rankings, etc.) Apps that recommend that users restart their iOS device prior to installation or launch may be rejected
37 Metadata (name, descriptions, ratings, rankings, etc.) Apps should have all included URLs fully functional when you submit it for review, such as support and privacy policy URLs
38 Locations Apps that do not notify and obtain user consent before collecting, transmitting, or using location data will be rejected
39 Locations Apps that use location-based APIs for automatic or autonomous control of vehicles, aircraft, or other devices will be rejected
40 Locations Apps that use location-based APIs for emergency services will be rejected
41 Locations Location data can only be used when directly relevant to the features and services provided by the App to the user or to support approved advertising uses
42 Push Notifications Apps that provide Push Notifications without using the Apple Push Notification (APN) API will be rejected
43 Push Notifications Apps that use the APN service without obtaining a Push Application ID from Apple will be rejected
44 Push Notifications Apps that send Push Notifications without first obtaining user consent, as well as apps that require Push Notifications to function, will be rejected
45 Push Notifications Apps that send sensitive personal or confidential information using Push Notifications will be rejected
46 Push Notifications Apps that use Push Notifications to send unsolicited messages, or for the purpose of phishing or spamming will be rejected
47 Push Notifications Apps cannot use Push Notifications to send advertising, promotions, or direct marketing of any kind
48 Push Notifications Apps cannot charge users for use of Push Notifications
49 Push Notifications Apps that excessively use the network capacity or bandwidth of the APN service or unduly burden a device with Push Notifications will be rejected
50 Push Notifications Apps that transmit viruses, files, computer code, or programs that may harm or disrupt the normal operation of the APN service will be rejected
51 Game Center Apps that display any Player ID to end users or any third party will be rejected
52 Game Center Apps that use Player IDs for any use other than as approved by the Game Center terms will be rejected
53 Game Center Developers that attempt to reverse lookup, trace, relate, associate, mine, harvest, or otherwise exploit Player IDs, aliases, or other information obtained through Game Center will be removed from the iOS Developer Program
54 Game Center Game Center information, such as Leaderboard scores, may only be used in Apps approved for use with Game Center
55 Game Center Apps that use the Game Center service to send unsolicited messages, or for the purpose of phishing or spamming will be rejected
56 Game Center Apps that excessively use the network capacity or bandwidth of Game Center will be rejected
57 Game Center Apps that transmit viruses, files, computer code, or programs that may harm or disrupt the normal operation of the Game Center service will be rejected
58 Advertising Apps that artificially increase the number of impressions or click-through of ads will be rejected
59 Advertising Apps that contain empty iAd banners will be rejected
60 Advertising Apps that are designed predominantly for the display of ads will be rejected
61 Trademarks and trade dress Apps must comply with all terms and conditions explained in the Guidelines for Using Apple Trademarks and Copyrights and the Apple Trademark List
62 Trademarks and trade dress Apps that suggest or infer that Apple is a source or supplier of the App, or that Apple endorses any particular representation regarding quality or functionality will be rejected
63 Trademarks and trade dress Apps that appear confusingly similar to an existing Apple product or advertising theme will be rejected
64 Trademarks and trade dress Apps that misspell Apple product names in their App name (i.e., GPS for Iphone, iTunz) will be rejected
65 Trademarks and trade dress Apps may not use protected third party material such as trademarks, copyrights, patents or violate 3rd party terms of use. Authorization to use such material must be provided upon request
66 Media content Apps that do not use the MediaPlayer framework to access media in the Music Library will be rejected
67 Media content App user interfaces that mimic any iPod interface will be rejected
68 Media content Audio streaming content over a cellular network may not use more than 5MB over 5 minutes
69 Media content Video streaming content over a cellular network longer than 10 minutes must use HTTP Live Streaming and include a baseline 64 kbps HTTP Live stream
70 User interface Apps must comply with all terms and conditions explained in the Apple iOS Human Interface Guidelines
71 User interface Apps that look similar to Apps bundled on the iPhone, including the App Store, iTunes Store, and iBooks Store, will be rejected
72 User interface Apps that do not use system provided items, such as buttons and icons, correctly and as described in the Apple iOS Human Interface Guidelines may be rejected
73 User interface Apps that create alternate desktop/home screen environments or simulate multi-App widget experiences will be rejected
74 User interface Apps that alter the functions of standard switches, such as the Volume Up/Down and Ring/Silent switches, will be rejected
75 User interface Apple and our customers place a high value on simple, refined, creative, well thought through interfaces. They take more work but are worth it. Apple sets a high bar. If your user interface is complex or less than very good, it may be rejected
76 Purchasing and currencies Apps that unlock or enable additional features or functionality with mechanisms other than the App Store will be rejected
77 Purchasing and currencies Apps utilizing a system other than the In-App Purchase API (IAP) to purchase content, functionality, or services in an App will be rejected
78 Purchasing and currencies Apps using IAP to purchase physical goods or goods and services used outside of the App will be rejected
79 Purchasing and currencies Apps that use IAP to purchase credits or other currencies must consume those credits within the App
80 Purchasing and currencies Apps that use IAP to purchase credits or other currencies that expire will be rejected
81 Purchasing and currencies Content subscriptions using IAP must last a minimum of 7 days and be available to the user from all of their iOS devices
82 Purchasing and currencies Apps that use IAP to purchase items must assign the correct Purchasability type
83 Purchasing and currencies Apps that use IAP to purchase access to built-in capabilities provided by iOS, such as the camera or the gyroscope, will be rejected
84 Purchasing and currencies Apps containing content or services that expire after a limited time will be rejected, except for specific approved content (e.g. films, television programs)
85 Purchasing and currencies Insurance Apps must be free, in legal-compliance in the regions distributed, and cannot use IAP
86 Purchasing and currencies In general, the more expensive your App, the more thoroughly we will review it
87 Purchasing and currencies Apps offering subscriptions must do so using IAP, Apple will share the same 70/30 revenue split with developers for these purchases, as set forth in the Program License Agreement
88 Purchasing and currencies Apps that link to external mechanisms for purchases or subscriptions to be used in the App, such as a “buy” button that goes to a web site to purchase a digital book, will be rejected
89 Purchasing and currencies Apps can read or play approved content (specifically magazines, newspapers, books, audio, music, video and cloud storage) that is subscribed to or purchased outside of the App, as long as there is no button or external link in the App to purchase the approved content. Apple will only receive a portion of revenues for content purchased inside the App
90 Purchasing and currencies Apps may only use auto renewing subscriptions for periodicals (newspapers, magazines), business Apps (enterprise, productivity, professional creative, cloud storage) and media Apps (video, audio, voice), or the App will be rejected
91 Purchasing and currencies Apps may enable additional approved features or functionality when used in combination with specific approved physical products (such as a toy) as long as the additional features and functionality are either completely dependent on such hardware (for example an App that is used to control a telescope) or also available through the App without the physical products, such as by way of reward for achievement or by use of IAP
92 Scraping and aggregation Apps that scrape any information from Apple sites (for example from apple.com, iTunes Store, App Store, iTunes Connect, Apple Developer Programs, etc.) or create rankings using content from Apple sites and services will be rejected
93 Scraping and aggregation Apps may use approved Apple RSS feeds such as the iTunes Store RSS feed
94 Scraping and aggregation Apps that are simply web clippings, content aggregators, or a collection of links, may be rejected
95 Damage or injury Apps that encourage users to use an Apple Device in a way that may cause damage to the device will be rejected
96 Damage or injury Apps that rapidly drain the device’s battery or generate excessive heat will be rejected
97 Damage or injury Apps whose use may result in physical harm may be rejected
98 Personal attacks Any App that is defamatory, offensive, mean-spirited, or likely to place the targeted individual or group in harm’s way will be rejected
99 Personal attacks Professional political satirists and humorists are exempt from the ban on offensive or mean-spirited commentary
100 Violence Apps portraying realistic images of people or animals being killed or maimed, shot, stabbed, tortured or injured will be rejected
101 Violence Apps that depict violence or abuse of children will be rejected
102 Violence “Enemies” within the context of a game cannot solely target a specific race, culture, a real government or corporation, or any other real entity
103 Violence Apps involving realistic depictions of weapons in such a way as to encourage illegal or reckless use of such weapons will be rejected
104 Violence Apps that include games of Russian roulette will be rejected
105 Objectionable content Apps that present excessively objectionable or crude content will be rejected
106 Objectionable content Apps that are primarily designed to upset or disgust users will be rejected
107 Privacy Apps cannot transmit data about a user without obtaining the user’s prior permission and providing the user with access to information about how and where the data will be used
108 Privacy Apps that require users to share personal information, such as email address and date of birth, in order to function will be rejected
109 Privacy Apps may ask for date of birth (or use other age-gating mechanisms) only for the purpose of complying with applicable children’s privacy statutes, but must include some useful functionality or entertainment value regardless of the user’s age
110 Privacy Apps that collect, transmit, or have the capability to share personal information (e.g. name, address, email, location, photos, videos, drawings, the ability to chat, other personal data, or persistent identifiers used in combination with any of the above) from a minor must comply with applicable children’s privacy statutes
111 Pornography Apps containing pornographic material, defined by Webster’s Dictionary as “explicit descriptions or displays of sexual organs or activities intended to stimulate erotic rather than aesthetic or emotional feelings”, will be rejected
112 Pornography Apps that contain user generated content that is frequently pornographic (e.g. “Chat Roulette” Apps) will be rejected
113 Religion, culture, and ethnicity Apps containing references or commentary about a religious, cultural or ethnic group that are defamatory, offensive, mean-spirited or likely to expose the targeted group to harm or violence will be rejected
114 Religion, culture, and ethnicity Apps may contain or quote religious text provided the quotes or translations are accurate and not misleading. Commentary should be educational or informative rather than inflammatory
115 Contests, sweepstakes, lotteries, raffles, and gambling Sweepstakes and contests must be sponsored by the developer/company of the App
116 Contests, sweepstakes, lotteries, raffles, and gambling Official rules for sweepstakes and contests must be presented in the App and make it clear that Apple is not a sponsor or involved in the activity in any manner
117 Contests, sweepstakes, lotteries, raffles, and gambling It must be permissible by law for the developer to run a lottery App, and a lottery App must have all of the following characteristics: consideration, chance, and a prize
118 Contests, sweepstakes, lotteries, raffles, and gambling Apps that allow a user to directly purchase a lottery or raffle ticket in the App will be rejected
119 Contests, sweepstakes, lotteries, raffles, and gambling Apps that offer real money gaming (e.g. sports betting, poker, casino games, horse racing) must have necessary licensing and permissions in the locations where the App is used, must be restricted to those locations, and must be free on the App Store
120 Contests, sweepstakes, lotteries, raffles, and gambling Apps that use IAP to purchase credit or currency to use in conjunction with real money gaming will be rejected
121 Charities and contributions Apps that include the ability to make donations to recognized charitable organizations must be free
122 Charities and contributions The collection of charitable donations must be done via a web site in Safari or an SMS
123 Legal requirements Apps must comply with all legal requirements in any location where they are made available to users. It is the developer’s obligation to understand and conform to all local laws
124 Legal requirements Apps that contain false, fraudulent or misleading representations or use names or icons similar to other Apps will be rejected
125 Legal requirements Apps that solicit, promote, or encourage criminal or clearly reckless behavior will be rejected
126 Legal requirements Apps that enable illegal file sharing will be rejected
127 Legal requirements Apps that are designed for use as illegal gambling aids, including card counters, will be rejected
128 Legal requirements Apps that enable anonymous or prank phone calls or SMS/MMS messaging will be rejected
129 Legal requirements Developers who create Apps that surreptitiously attempt to discover user passwords or other private user data will be removed from the iOS Developer Program
130 Legal requirements Apps that contain DUI checkpoints that are not published by law enforcement agencies, or encourage and enable drunk driving, will be rejected
131 Legal requirements Apps that calculate medicinal dosages must be submitted by the manufacturer of those medications or recognized institutions such as hospitals, insurance companies, and universities
132 Passbook Passbook Passes can be used to make or receive payments, transmit offers or offer identification (such as movie tickets, airline tickets, coupons and reward offers). Other uses may result in the rejection of the App and the revocation of Passbook credentials
133 Passbook Passes must include valid contact information from the issuer of the pass or the App will be rejected and Passbook credentials may be revoked
134 Passbook Passes must be signed by the entity that will be distributing the pass under its own name, trademark, or brand or the App will be rejected and Passbook credentials may be revoked
135 Kids Category Apps primarily intended for use by kids must include a privacy policy and must comply with applicable children’s privacy statutes
136 Kids Category Apps primarily intended for use by kids may not include behavioral advertising (e.g. the advertiser may not serve ads based on the user’s activity within the App), and any contextual ads presented in the App must be appropriate for kids
137 Kids Category Apps primarily intended for use by kids must get parental permission or use a parental gate before allowing the user to link out of the app or engage in commerce
138 Kids Category Apps in the Kids Category must be made specifically for kids ages 5 and under, ages 6-8, or ages 9-11

AirDroid and Diawi

Don’t fight for USB cables, feel free to use AirDroid app and Diawi

Air Droid

test2

     AirDroid, an awesome free app and helps to take screen shot on Android devices. You can capture those images wirelessly via your web browser. AirDroid can control many other aspects of your device from a browser, too.

     AirDroid for Android replaces your USB cable with your web browser. Transfer files back and forth, send text messages, play music, view your photos and manage applications — all without installing anything on your computer.

     AirDroid is completely free; it doesn’t even contain ads. It functions as a web server, allowing your. Android device and your computer to communicate over the network.

Please go through the below link:
App link: https://play.google.com/store/apps/details?id=com.sand.airdroid
Configuration details: http://www.howtogeek.com/105813/

Diawi (Development iOS Apps Wireless Installation)

test1

     Diawi is based on Apple’s wireless distribution model introduced in iOS 4 to allow development application installation without iTunes or even a computer. After the upload, Diawi creates a unique short URL to access the installation page (for ex: aBcDeF). When opened in Safari on the iOS device, the page will display a link to install the application. This feature allows to quickly deploying applications to testers, clients, medias, bloggers or friends without the need to send large files by e-mail.

     The installation using Diawi is a lot easier than through iTunes or the iPhone Configuration Utility: a simple URL and only 1 tap are needed. The iOS build (.ipa) should be provisioned before uploading to diawi. Otherwise Diawi will show error message.

For more information: http://www.diawi.com/

Test Metrics

software-testing-company-1234

     Test Metrics is most important to measure the quality, cost and effectiveness of the project and the processes. Without measuring these, project can’t be completed successfully. Test metrics helps,

  • To take the decision for next phase of activities such as, estimate the cost & schedule of future projects.
  • To understand the kind of improvement required to success the project.
  • Take decision on process or technology to be modified.

Different Types of Test Metrics

Base Metrics (Direct Measure)

    Base metrics constitute the raw data gathered by a Test Analyst throughout the testing effort. These metrics are used to provide project status reports to the Test Lead and Project Manager; they also feed into the formulas used to derive Calculated Metrics.

Base Metrics Test Phases
# of Test Cases Test Development Phase
# of Test Cases Executed Test Execution Phase
# of Test Cases Passed Test Execution Phase
# of Test Cases Failed Test Execution Phase
# of Test Cases Under Investigation Test Development Phase
# of Test Cases Blocked Test dev/execution Phase
# of Test Cases Re-executed Regression Phase
# of First Run Failures Test Execution Phase
Total Executions Test Reporting Phase
Total Passes Test Reporting Phase
Total Failures Test Reporting Phase
Test Case Execution Time Test Reporting Phase
Calculated Metrics (Indirect Measure)

    Calculated Metrics convert the Base Metrics data into more useful information. These types of metrics are generally the responsibility of the Test Lead and can be tracked at many different levels (by module, tester, or project).

Calculated Metrics Test Phases
% Complete Test Reporting Phase or Post test Analysis phase
% Defects Corrected Test Reporting Phase or Post test Analysis phase
% Test Coverage Test Reporting Phase or Post test Analysis phase
% Rework Test Reporting Phase or Post test Analysis phase
% Test Cases Passed Test Reporting Phase or Post test Analysis phase
% Test Effectiveness Test Reporting Phase or Post test Analysis phase
% Test Cases Blocked Test Reporting Phase or Post test Analysis phase
% Test Efficiency Test Reporting Phase or Post test Analysis phase
1st Run Fail Rate Test Reporting Phase or Post test Analysis phase
Defect Discovery Rate Test Reporting Phase or Post test Analysis phase
Overall Fail Rate Test Reporting Phase or Post test Analysis phase

Formulas for Calculating Metrics

  1. %ge Test cases Executed: This metric is used to obtain the execution status of the test cases in terms of %ge.

%ge Test cases Executed = (No. of Test cases executed / Total no. of Test cases written) * 100.

  1. %ge Test cases not executed: This metric is used to obtain the pending execution status of the test cases in terms of %ge.

%ge Test cases not executed = (No. of Test cases not executed / Total no. of Test cases written) * 100.

  1. %ge Test cases Passed: This metric is used to obtain the Pass %ge of the executed test cases.

%ge Test cases Passed = (No. of Test cases Passed / Total no. of Test cases Executed) * 100.

  1. %ge Test cases Failed: This metric is used to obtain the Fail %ge of the executed test cases.

%ge Test cases Failed = (No. of Test cases Failed / Total no. of Test cases Executed) * 100.

  1. %ge Test cases Blocked: This metric is used to obtain the blocked %ge of the executed test cases. A detailed report can be submitted by specifying the actual reason of blocking the test cases.

%ge Test cases Blocked = (No. of Test cases Blocked / Total no. of Test cases Executed) * 100

  1. Defect Density is a measure showing the ratio of defects. against the size of a development. Size is typically expressed in terms of Function Points or Impact Points

Defect Density = No. of Defects identified / size

(Here ‘Size’ is considered as requirement. Hence here the Defect Density is calculated as number of defects identified per requirement).

  1. DRE (Defect Removal Efficiency) is used to identify the test effectiveness of the software.

Defect Removal Efficiency (DRE) = (No. of Defects found during QA testing / (No. of Defects found during QA testing + No. of Defects found by End user)) * 100

  1. Defect Leakage: Defect Leakage is the Metric which is used to identify the efficiency of the QA testing i.e., how many defects are missed / slipped during the QA testing.

Defect Leakage = (No. of Defects found in UAT / No. of Defects found in QA testing.) * 100

  1. Defects by Severity/Priority: This metric is used to identify the no. of defects identified based on the Severity / Priority of the defect which is used to decide the quality of the software.
  • %ge Critical Defects = No. of Critical Defects identified / Total no. of Defects identified * 100
  • %ge High Impact Defects = No. of High Impact Defects identified / Total no. of Defects identified * 100
  • %ge Medium Impact Defects = No. of Medium Impact Defects identified / Total no. of Defects identified * 100
  • %ge Low Impact Defects = No. of Low Impact Defects identified / Total no. of Defects identified * 100
  • %ge High Priority Defects = No. of High Priority Defects identified / Total no. of Defects identified * 100
  • %ge Medium Priority Defects = No. of Medium Priority Defects identified / Total no. of Defects identified * 100
  • %ge Low Priority Defects = No. of Low Priority Defects identified / Total no. of Defects identified * 100

Life with Bug Tracking Tools

tracking-bugs-with-intervals-online-task-management-software


I would like to share small information about the bug tracking or project management tools


Salesforce (https://login.salesforce.com/?locale=in) – is a web-based project management as well as bug tracking system, it is very effective in software quality assurance. The platform supports tasks planning, creating stories to track tasks as well as various reports and statistics. I used this tool for defect tracking, defect cloning and work hours burning. The other features of this tool include:

  • Project.
  • Stories.
  • Clone defects.
  • Defect sharing.
  • Kanban (Story-wise and project-wise), to helps companies visualize workflow, analyze and improve business processes and reduce waste.
  • Chatter.
  • Defects.
  • Burn Work Hours.
  • Reports.

Unfuddle (https://unfuddle.com) – is a secure, defect tracking and project management solution. Developers can commit the source code. I used this tool for tracking defects in 2011-2012 in my software testing life. Look and feel is good, easy to use. The other features of this tool include:

  • Web-based Subversion access.
  • Milestone tracking.
  • Bug and issue management.
  • Wiki.

JIRA (https://www.atlassian.com/software/jira) – is a branded issue tracking product, developed by Atlassian, used for bug tracking and project management. Developers can commit the code. I used this tool for tracking defects in 2012-2013. The other features of this tool include:

  • Code Integration.
  • Project Tracking.
  • Issues Tracking.
  • Process (Software development workflow).
  • Planning (JIRA to help capture, assign, and prioritize their work).
  • Wiki.

image2014-3-13 14-48-34     logo180     image2014-3-13 14-49-46

Team Foundation Server (TFS) – It manages repositories, build processes, testing infrastructure, and lab deployment all while easily collaborating and reporting status. Team Foundation Server supports connects, collaborate, and deliver on time. Created to get more out of development teams, Team Foundation Server (TFS) 2013 is the application lifecycle management hub for Visual Studio. It enables all stakeholders to participate in the development process using a single solution. Use it to manage heterogeneous projects and teams as well. The other features of this tool include:
  • Project.
  • Stories.
  • Version Control.
  • Agile Planning & Collaboration.
  • Build.
  • Test Case Management.
  • Reporting.

Axosoft (http://www.axosoft.com/bug-tracker) – (formerly OnTime) is a proprietary project management and bug tracking system, available as hosted or on-premises software. Project managers and developers are able to visually see each task, requirement, defect and incident in the system on individual filing cards through the Scrum planning board. I am using this tool for tasks creations, defect tracking, add work logs. The other features of this tool include:

  • Bug tracking
  • Requirements management
  • Scrum planning board
  • Scrum burndown charts
  • Team wiki
  • Help desk/incident tracking
  • Workflow automation
  • Reporting
  • Data visualization
  • SCM integration

Project Locker (https://portal.projectlocker.com) – is web-based project management and bug tracking with Trac. This tool was used for tracking defects, subversion hosting. Trac was my first bug tracking tool. The other features of this tool include:

  • Project management (Roadmap, Milestones, etc.).
  • Ticket system (bug tracking, tasks, etc.).
  • Search engine for tickets.
  • Email notifications.
  • Wiki with attachments.
  • Version control system.

axosoft-logo-black@2x     Visual_Studio_2012_logo_and_wordmark.svg     image2014-3-13 14-48-23

Mantis – is an issue tracking system and project management tool. I used this tool for storing my test scripts; it helped me to store the test scripts in structured manner with different Test Suites. The other features of this tool include:
  • E-mail notifications upon changes being made to issues in the system.
  • Version control system.
  • Roadmap.
  • Wiki.
  • Change Log.

TestLink (http://testlink.org/) – is a web-based test management system, it is very effective in software quality assurance. The platform offers support for test cases, test suites, test plans as well as various reports and statistics. I used this tool for creating test plan, test suite and test cases. The other features of this tool include:

  • User roles and management.
  • Grouping of test cases in test specifications.
  • Test plans.
  • Platforms.
  • Requirements with versioning.
  • Support for testing different builds of the software.
  • Reports and charts.
  • Bug tracking system integration (Mantis, JIRA, and others).

Assembla (https://www.assembla.com/) – is web-based project management, code management and bug tracking system. Assembla using a distributed agile process to link employees from multiple locations. Assembla Workspaces provide development teams with tools including: task management, code repositories, real-time collaboration, and deployment tools. The other features of this tool include:

  • Tickets.
  • Wiki.
  • StandUp.
  • Messages.
  • Files.
  • SVN.
  • Team.
  • Stream.
  • Admin.

image2014-3-13 14-50-10     image2014-3-13 14-50-1     image2014-3-13 14-49-28