EDI Testing, Database Testing, quality center implementation, Functional Testing services, Web Testing service,  validation services, Black Box Testing, Desktop Application Testing , Facebook App Testing, White Box Testing, Data Warehouse Testing , UI Testing,
Data Migration Testing, Reports Testing, Mobile Testing Services, Mobile Testing Company, Exploratory Testing, Datawarehouse Testing, outsource software testing, SAP testing services, software testing services, Usability Testing company , application testing company, web testing company, Beta Testing company , qa staffing, Web Compatibility Testing, Mobile Compatibility Testing, crowdsourcing testing, qa resources, QA On Demand, Performance Testing company , Test Automation service, Software QA Engineers, qa resume, Performance Testing Services , top software testing companies, qa companies, Validation Testing , software testing companies,

Spread the word:

facebook   twitter   linkedin  

EDI Testing, Database Testing, quality center implementation, Functional Testing services, Web Testing service,  validation services, Black Box Testing, Desktop Application Testing , Facebook App Testing, White Box Testing, Data Warehouse Testing , UI Testing,
Data Migration Testing, Reports Testing, Mobile Testing Services, Mobile Testing Company, Exploratory Testing, Datawarehouse Testing, outsource software testing, SAP testing services, software testing services, Usability Testing company , application testing company, web testing company, Beta Testing company , qa staffing, Web Compatibility Testing, Mobile Compatibility Testing, crowdsourcing testing, qa resources, QA On Demand, Performance Testing company , Test Automation service, Software QA Engineers, qa resume, Performance Testing Services , top software testing companies, qa companies, Validation Testing , software testing companies,

Spread the word:

facebook   twitter   linkedin  

Software QA and Testers

May 11, 2012

I am pleased to announce our next QA Meetup on May 28, 2012 @ 6pm in our San Francisco office at 12 Geary St #207, SF, CA 94116.

Thank you all who came out to our April event. Many folks wanted to chat about various testing methodologies and talk about advantages and disadvantages and share our experiences.

We will geek out on QA methodologies, test automation topics and venture into some load and performance concerns.

We’re informal, community centric, and much more hip than other QA groups

Please join us whether you are exploring,  interested in learning how to get started, or looking for QA or Testing experts, or you are, in fact,  a seasoned pro looking for a tribe. Click Here to RSVP

Spread the word:

facebook   twitter   linkedin  

Why more than 500 clients have chosen our solution over other expensive test automation software?

SQA Solution is the only software testing company you need for all types of software testing. We test software at any level: unit testing, system integration testing, system testing, regression or UI testing.  Our team can automate black box testing, acceptance testing, keyword or data-driven testing. We also develop test scripts for compatibility tests and functional tests.

SQA Solution test automation architects  will help you with automating everything from individual component testing to full regression suites. Depending on individual automation goals, we work with clients to create custom test automation solutions.

Our Test Automation Capabilities

	J Meter		Selenium,
	Borland Silk Test		Database Opensource Test Suite
	QTP		Cucumber
	Microsoft Rational Robot		Load Runner
	Silk Performer		Test Bench
	WebLoad		Compuware
	Test Load		Http Load
	Selenium Grid		Python/Nose
	Grinder		eggplant
	JUnit		FlexUnit

Powerful state-of-the-art skills make us the only software testing company you need. Our clients experience significant cost savings by leveraging our On-Demand services and by letting us help them improve the way they test by reducing QA overhead.

	Control	Test early, test robustly and offload costly overhead.
	Customization	What you need when you need it where you need it. Customers test when it fits their schedule, with no long-term contracts or commitments
	Savings	QA solution for a lot less than hiring additional staff members or contractors
	Increase Application Quality	Testing earlier, smarter, and faster by leveraging RentTesters experienced Web  Application testing resources throughout your development cycle.
	Accelerate Time-to-Market	Finding critical issues earlier and preventing delays that are caused by issues found late. Bugs detected and fixed early are less expensive and keep your project quality up and costs down.
	Minimize Testing Costs	Pay only for what you need with RentTesters On-Demand delivery model allowing you to tailor your testing solution to focus your budget dollars where they’re most needed.
		View All Services

Spread the word:

facebook   twitter   linkedin  

JIRA MOBILE CONNECT - https://plugins.atlassian.com/plugins/com.atlassian.jconnect.jconne…

It is accessible via xCode simply connect your iad to a mac book and you can view all the apps log files(including crash).

Crash logs stored in app folder structure :

Documents/ Library/ Preferences/ MyApp.app/ Default.png icon.png Info.plist tmp/

Logs are also available  in Windows just connect your iphone to PC and navigate to t:

Users/ApplicationData/Roaming/AppleComputer/Devicename/

Spread the word:

facebook   twitter   linkedin  

We will geek out on QA methodologies, test automation topics and venture into some load and performance concerns.

We’re informal, community centric, and much more hip than other QA groups

Please join us whether you are exploring,  interested in learning how to get started, or looking for QA or Testing experts, or you are, in fact,  a seasoned pro looking for a tribe.

Bring your challenging problems and questions and let me know that you’d like to discuss and we’ll consider it as a group.

Agenda: TBD

RSVP to QA April Meetup

Spread the word:

facebook   twitter   linkedin  

What will be the basis for performing a risk assesment while applying patches?

In a regular system implementation or upgrade or enhancement, the risk assessment is based on URS or FS to determine the extent of validation testing required.  To discuss criteria for performing risk assessment I asked SQA Solution folks to establish a risk assessment checklist for applying a patch.

Based on the output of this RA, I would determine the extent of testing and regression testing required.  The patches usually come with technical description / release notes of what they are fixing. If they are patches then they are not necessarily ‘changing’ functionality but ‘fixing’ existing functionality to how it should have been. An example we had was date format could not be changed within in the system, even though the functionality was stated it could in the design. A patch was applied post go live and we had to verify the results did not impact quality critical data (there were a lot of functions using the date in the system). We tested all quality critical modules (by type, not every instance) using the date format and a statistical testing method to verify the data.
The risk assessment determines whether/how these fixes affect critical functions and yes, the extent of verification. Is best for such patches to be tested in a sandbox system to ensure nothing obvious is wrong before updating the live system and verifying results.

The system should also have a procedure for patch management as part of the deliverables, if it doesn’t you might want to consider developing one (there are many templates depending on system type). If it does have an SOP, it should give you the necessary guidance (if it is not good enough then refer to writing one).

The following may be considered as an example for performing a risk assessment applying to patches.

Vulnerability – The vendor has identified flaws in the security design of the system; however, new patches have not been applied to the system

Threat – Unauthorized users (e.g., hackers, disgruntled employees, computer criminals, terrorists)

Threat Action – Obtaining unauthorized access to sensitive system files based on known system vulnerabilities

Based upon the purpose of the ‘patch’, and a change impact assessment which carefully reviews the release notes), some patches
- Are automatically applied to Production (e.g. anti-virus definition updates)
- Are manually applied to Production with no testing (e.g. critical security patch for the operating system)
- Are applied first in a QA/Test instance, with limited or no regression testing (e.g. minor application bug fix)
- Are applied first in a QA/Test instance,with more extensive regression testing (e.g. major application fix)
- Are applied in a development environment, configuration changes made, then promoted to QA/test for more extensive testing (e.g. major application upgrade)

For all of these, the User Requirements need not have changed.

Also see Appendix S4 in GAMP 5 (Patch and Update Management).

We generally look at risk / impact analysis of changes to the infrastructure along three dimensions: error – failure – threat. Error is “Oops!” and the realm of things like HACCP. Failure is the realm of “What was that?!?!” and the realm of FMEA, and threat is the realm of the guys In the black hats and Fites-Kratz. etc.

I will leave you to negotiate with whomever as to whether or not you actually have to generate any of these.

Speaking as a software engineer / CISSP, for your situation, I’d recommend an in-service qualification rollout of your patches to a subset of low-criticality systems with careful, well-documented monitoring of functional and operational performance. That is, pick a few non-product-quality systems, apply the patches, exercise them, make sure the numbers add up, and throw a heavy load at them to be sure they don’t buckle under the stress. (NOTE: Do this at 3:00 AM – The voice of experience speaks!)

As you become more confident that the patch is holding water, venture into deeper, rougher waters by rolling the patches onto higher criticality systems, until you have all of the boxes done. Again, document thoroughly. You are, in essence, doing “live fire” regression testing.  A further point is that Risk Assessment should cover the risk of applying the patch versus the risk of NOT applying the patch. A simple example is an OS update where a security flaw has become apparent and there are known exploits in operation. In such circumstances the risk of problems from applying the patch is likely to be low (we can reasonably expect it has been tested by the OS developer) whereas there is high vulnerability of the unpatched system. In such circumstances applying immediately is a defensible position

Spread the word:

facebook   twitter   linkedin  

SAS is a standard product, so it needs Installation Qualification and Change Control.

You need to put much more effort in the design and verification of the custom programs for analyses and reports that you (or the statisticians) develop using SAS as the tool. Those are the risky ones.
Need to comply with Part 11 depends on the type of use. For example, we just couple it with a Version Control system to implement security and audit trail of the custom programs, but we manage the data with other software, and SAS comes into play only at the very end of the process.

You should audit SAS to verifiy their testing of the Base SAS procedures and qualify the installation of the infrastructure and Base SAS software. SAS are happy to host audits at any time (I was just in Cary with SAS last week).

You should then focus your efforts on the risk-based validation of your SAS programmes and it is here that you should focus your efforts defining User Requirements.

It’s relatively easy to write a Validation Master Plan to define this approach, and then a relatively simple Validation Plan (etc) for each suite of SAS programmers. This would depend on what you were intending to use SAS for; but, unless you are doing something quite different with the product, then I would say that your Vendor Assessment could be restricted to a review of public information regarding the establishment and trusted nature of the product. SAS is so low risk that I would not consider a formal audit to be necessary – my approach would be to read the vendor documentation – user guides and release notes, etc. and carry out a documented risk assessment to show that my intended application of the various software modules was within it’s designed scope and there were no known issues.
Then I would spend all your time on working on the validation process for the programs that you are going to write with the software – that is where all your real risk lies. IQ and so on for SAS itself and careful specs and risk assessments for any SAS programs making part of your system.
I was involved in doing this for a large SAS system and I would say you need to add a Version control system to control your data and programs. This is not really because of CFR 21 part 11 (although it does cover the auditing part of that) but because the FDA can ask you to reproduce past outputs and this is a stronger requirement on a production system. By itself SAS does not cover this need. (and I am aware of SDD and versioning in the Clin reporting tool).

You are getting good advice here If you want more detail you can contact me I am free at the moment.

Spread the word:

facebook   twitter   linkedin  

RentTesters is a leader in software testing services, software quality assurance services,  load and performance testing services that empowers organizations to build high quality software for their customers and end users. Our engineers have many years of experience in QA and are experts in software testing and performance testing solutions and methodologies with a common goal to save time, reduce costs, and maximize quality.

RentTesters has multiple locations in San Francisco, Los Angeles, and in India and Ukraine.

With this vision, RentTesters formed strategic partnerships with both HP and IBM providing powerful and affordable solutions giving companies more tools and resources required to work more productively and efficiently accelerating ROI. This partnership allows our clients to leverage and apply collective experiences to effectively address mission critical business priorities, challenges, and tasks. RentTesters is an authorized re-seller and can consult with you to choose the right tools and help implement seamlessly.

Why Choose Us

RentTesters offers wide range of software testing services to assure the success of our clients’ projects while getting the highest level of Return on Investment. RentTesters leverages proven test strategy for our customers built upon highest standards of test processes towards building successful testing. RentTesters works with clients to independently assess current state of testing from strategic and operational perspectives, and set testing goals to transform their testing. Over the years, our experience in software testing has widened our range of services and today includes:

Contact Us to get detailed information about what’s included in our services. Request a quote from us today!

Spread the word:

facebook   twitter   linkedin