Showing posts with label software testing. Show all posts
Showing posts with label software testing. Show all posts

Tuesday, 4 July 2017

Learning Management System Compliance




A very common scenario that any learning management system (LMS) vendors experience is, “A potential client reaches at their exhibition booth and asks, “Is your LMS complies with regulatory standards?”
The answer is not very simple.
The worry with compliance is that it is driven by laws and regulations, which require specific training. The desire of companies is to avoid liabilities, business objectives implementation, reduction of paperwork.
To understand the topic thoroughly, we have to differentiate between the ability to track compliance in a number of areas and as a piece of software, a learning management system should be compliant with certain standards and regulations. It is crucial to understand that laws and regulations are explicit to individual countries or states, and will vary widely from one jurisdiction to another.
The below definitions and examples are drawn from the United States and Canada but there will be similar issues in the regulation of other countries as well.
Below are main compliance issues that a learning management system vendor needs to consider:
Accessibility standards – In the United States, accessibility regulations come under the Americans with Disabilities Act (ADA) and Section 508 (29 U.S.C. ‘794d) of the 1998 Rehabilitation Act. These standards follow the World Wide Web Consortium’s (W3C) Web Content Accessibility Guidelines 1.0. LMS adhering to these standards will help to increase the user base.
Regulatory compliance tracking – LMSs are basically large databases and are often questioned to track regulatory compliance with specific government regulation.
Example: In United States, Health Insurance Portability and Accountability Act (HIPAA), and the Occupational Safety and Health Administration (OSHA) regulations are included.
In Canada, the requirements of training for the Workplace Hazardous Materials Information System (WHIMIS) are at times tracked by an LMS.
Security standards – Many organizations require secured systems to store personal information. This is true in the medical field but can apply in other areas as well.
These requirements will include
  • maintenance of audit trails,
  • deployment of completely closed systems,
  • usage of digital signatures, such as the US Federal Drug Administration regulation FDA 21 CFR Part 11 for the medical, biotech, and pharmaceutical industries,
  • use of high degrees of encryption for groups such as the banking industry.
Interoperability standards – One of the most basic demands of LMS users is the interoperability of courses developed by different developers in the same LMS. It led to the development of one of the first set of LMS standards like those of the Aircraft Industry CBT Committee (AICC). In 1997, the IMS Global Learning Consortium (IMS GLC), a non-profit organization keen in setting stipulations and standards for the learning industry, was formed. It issued many sets of specifications since that date. In the same year the announcement of the Advanced Distributed Learning (ADL) initiative of the US Department of Defence. ADL developed the Shareable Content Object Reference Model (SCORM) and the ADL Registry of SCORM compliant software. LMS vendors are well aware of both AICC and SCORM, and generally are compliant with both standards.
However, most LMS implementations don’t work well with these standards and often require a period of adjustment and tuning to make them work seamlessly.
Tracking training for certification – There are many regulatory compliances for training in specific industries, where employees are required to be certified before being employed and require to be recertified on a regular basis. Many LMSs track certification and will trigger automatic alerts as the date for recertification approaches. This need can be driven by legislation or by standards imposed by a specific industry or company.
Tracking training for liability reduction – Training can aid reduce the liability for employers in controversial areas. Courses or educational materials on such things, such as sexual harassment, or employment discrimination; might be much less expensive to provide than a settling of lawsuits in case of disputes.
Reduction in paperwork – In conclusion, a fully functional LMS will have features that reduce workload and paperwork for compliance management. Such features include auto-enrolment in compliance training based on job, automated alerts to managers and workers on failure to complete compliance training, assessment and evaluation of the training, certificate issue on training completion, and many other configurations for tracking and reporting in this area.
So the answers to questions on compliance and learning management systems are not simple and are multidimensional.
Hopefully, this article will help you to sort out what you need in this area.

Friday, 2 June 2017

Testing a CRM Application

testing-crm-application
CRM systems are progressively becoming strategic assets for organizations, helping them manage the entire customer life-cycle, streamline operations and improve customer satisfaction.
According to Gartner, CRM implementation failure rates exceed 50% due to lack of effective CRM strategy and user adoption.
Ensuring a successful CRM implementation requires focus on business objective, robust business processes and a focus on the Quality of implementation.
An independent Quality Assurance and Testing process helps identify real challenges for CRM implementation, assess robustness and ensure adherence to user requirements. This results in higher success rate. Having a verification and validation Testing Team helps achieve greater quality in terms of both technical & business specifications and higher ROI.
A buggy or improperly implemented feature of a CRM application can have direct impact on customer relationship and hurt the revenue. Equally, a well-implemented CRM can help you gain customer insight and improve customer satisfaction and loyalty.
CRMs also contain a lot of sensitive data about company as well as customers. Any CRM testing program should ensure that the data are accurate and secure during the storage and retrieval transactions.
A typical CRM work flow will look like the below demonstrated image.
workflow-crm
indiumsoft-testing
Testing Cycles for a CRM Application

Data Integrity and Conversion Check

The first test cycle in CRM testing should focus on issues related to data quality and conversion. At every step of a migration or update the testers should verify that the CRM is working as expected for both with and without data.
Below is the check list to ensure data quality:
  1. Duplication of data: No redundancy should be allowed.
  2. Hidden data is indeed hidden: Only the appropriate data should be visible according to the user roles and type.
  3. Data maps correctly: Grid issues where a selected row’s data goes out of alignment with the fields when scrolled down. This should be eliminated.
  4. New and updated data should be saved properly: Customer information and card information should save and update properly.
  5. Partial and full search work as desired: Users should be able to search by first name, last name, company, card is deemed necessary.
  6. No data is missing: All of the required data should be available to the right user levels.
  7. Graphs should represent data correctly: Critical data like store-specific and program-specific filters and sales percentages should be accurate.
  8. Data sorting: All of the fields that need to be sortable should works as desired.
  9. CRM installs correctly: No critical GUI issues should arise during installation even when the user misses the data during installation.
  10. Data saved in one field does not move to another field after saving it: Fields like address, which may need more than one field, should save to the correct fields.
  11. Check that data which is not supposed to be editable is indeed not editable: Data like date and time of transaction should not be editable.

Functional Testing

This deals with the application’s function and ensures that it fits during the migration of data from another legacy system. The values and other data should be populated in the correct fields.
Below is functional checklist for CRM Testing –
  • Organization wide default
  • Access level
  • Accessible to hidden data
  • Transaction processes
  • Connection lost
  • Proper exception handling
  • Avoid data mismatch
  • Pre-Authorization
  • Post-Authorization

Performance Testing

The CRM application should be tested under pressure or stress or load. This can measure the effects of concurrent users on the system’s performance.
Performance Check List for CRM Testing –
  • Response time
  • Server utilization
  • Peak hours testing
  • Loading speed
  • Error with any other integrated applications due to this
  • Maximum number of users

Integration Testing

This will be a challenge in CRM applications where we will be migrating or integrating third party applications into the CRM.
Listed are the must see features during integration testing of a CRM
  • Field and Labels matching
  • Dependencies Integration
  • Date format
  • Reports
  • Data Validation
  • Sorting order

Regression Testing

There will be regression testing always in an application like CRM where there is a need to test before migration and after migration. After migration whether the values are populated into the correct fields and validations are matched with the data. Other fields should not be disturbed because of this. This will measure Functional correctness and completeness of the CRM application. With the help of regression testing the reliability and performance of the application can be ensured.

Security Testing

CRM involves high volume of confidential data which should be secured. A proper security test plan allows how well the system protects the data against unauthorized internal and external access.
Are you into CRM Testing?