We can offer quick, up-to-date professional advice on your QA – Software Testing resume and cover letter at our popular QA – Software Testing Resume Review sessions. We will review your QA – Software Testing resume and let you know how you can make it more effective.

Resume is the only thing that represents you in your dream company at the very beginning. Writing resume isn’t  a rocket science, but most people do not do well.

We can help! Here is how.

REVIEW

EDIT

SUBMIT

Professional proofreader at SQA Solution reviews your QA – Software Testing resume and provide you with edit suggestions. You then modify your resume according to the suggestions and get back to us for another review.  After the thumbs-up from the reviewer, you can the submit your resume to your dream company.

For your Resume Review session appointment make sure you:

  • Bring a paper copy of your resume or cover letter; usually only one can be reviewed in the time allocated.
  • Check-in at reception when you arrive; if you are more than 10 minutes late, you will have to reschedule.

 

download

#SQASolutionShare on FacebookShare on Google+Share on LinkedInTweet about this on TwitterEmail this to someone

SFDC Quiz

by admin on May 13, 2015

SFDC Interview Questions

SFDC Interview Questions

Question Excerpt
1.  Workflow rules can perform which of the following actions using standard Salesforce.com functionality?
A.
B.
C.
D.
2.  The Organization ID (Org ID) of a sandbox environment is the same as its production environment.
A.
B.
3.  Jim is a Salesforce.com system administrator for Universal Products Inc (UPI).  UPI currently uses org-wide public read/write for accounts. The sales department is concerned with sales reps being able to see each other’s account data, and would like sales reps to only be able to view their own accounts.  Sales managers should be able to view and edit all accounts owned by sales reps. The marketing department at UPI must be able to view all sales representative’s accounts at UPI. What steps must be configured in order to meet these requirements?
A.
B.
C.
D.
4.  The Data Loader can be used with Group Edition.
A.
B.
5.  What type of object relationship best describes the relationship between Campaigns and Leads (using standard Salesforce functionality)?
A.
B.
C.
6.  Which of the following are valid Salesforce license types?
A.
B.
C.
D.
E.
F.
7.  Which of the following are either current or future planned offerings by Salesforce.com or its subsidiaries?
A.
B.
C.
D.
E.
8.  Bob is a Salesforce.com consultant and is responsible for the data migration of an implmentation for his client, Universal Systems Inc (USI). USI wants to migrate contacts and accounts from their legacy CRM system, which has a similar data model (many contacts per one account; primary keys exist on contact and account). USI has provided Bob an export in CSV format of contacts and accounts of their legacy CRM system. What method should Bob use to migrate the data from the legacy system into Salesforce?
A.
B.
C.
9.  Universal Products Inc (UPI) wants to perform a drip marketing campaign on leads generated through website submissions.  What is the ideal method to execute this type of campaign?
A.
B.
C.
10.  Which of the following are valid ways to migrate metadata?
A.
B.
C.
D.

#SQASolutionShare on FacebookShare on Google+Share on LinkedInTweet about this on TwitterEmail this to someone

Concolic testing, also known as directed automated random testing (DART) or dynamic symbolic execution, is an efficient way to automatically and systematically generate test inputs for programs. Concolic testing uses a combination of runtime symbolic execution and automated theorem proving techniques to automatically generate non-redundant and exhaustive test inputs.  Specifically, concolic testing performs symbolic execution along a concrete execution path, generates a logical formula denoting a constraint on the input values, and solves a constraint to generate new test inputs that would execute the program along previously unexplored paths.

A key goal of concolic testing in the context of software testing is to explore as many different program paths as possible in a given amount of time, and for each path to (1) generate a set of concrete input values exercising that path, and (2) check for the presence of various kinds of errors including assertion violations, uncaught exceptions, security vulnerabilities, and memory corruption. The ability to generate concrete test inputs is one of the major strengths of concolic testing: from a test generation perspective, it allows the creation of high-coverage test suites, while from a bug-finding perspective, it provides developers with a concrete input that triggers the bug, which can be used to confirm and debug the error independently of the symbolic execution tool that generated it.

Concolic testing has inspired the development of several industrial and academic automated testing and security tools such as PEX, SAGE, and YOGI at Microsoft, Apollo at IBM, Conbol at Samsung, and CUTE, jCUTE, CATG, Jalangi, SPLAT, BitBlaze, jFuzz, Oasis, and SmartFuzz in academia.  A central reason behind the wide adoption of concolic testing is that, while concolic testing uses program analysis and automated theorem proving techniques internally, it exposes a testing usage model that is familiar to most software developers.

#SQASolutionShare on FacebookShare on Google+Share on LinkedInTweet about this on TwitterEmail this to someone

Class Demo and QA Boot camp Open House

by admin on March 2, 2015

Do you have QA openings?

Come and interview our QA Boot camp graduates.

What is QA Boot camp?

QA Bootcamp trains highly motivated individuals in web and mobile application testing and test automation. We teach best practices in Java, JUnit, TestNg, Selenium WebDriver, Git, SQL, and Test-Driven Development. Our learning environment includes pair testing, project based discovery, and a relentless focus on teamwork. At the completion of the 6 week program, students will have spent  over 200 hours in a hands-on,  intensive learning environment , coding test scripts to real problems and working on real projects.

QA Demo (Demo Day + Networking)

At the end of the program, QA Bootcamp is conducting a QA Demo day. A select handful of companies will be invited to watch students present their group projects. Afterwards you will have an opportunity to meet with the “Boots”. Employers are encouraged to set up interviews with graduates. Our fee is 10% of the salary of any QA Bootcamp graduates hired through our employer network and events.

QA Bootcamp’s Demo takes place Thursday, March 27, 2014 6:00 PM to 10:00 PM.  Click Here to register. Please be on time. Snacks and refreshments will be served.

**PLEASE NOTE — This is not an open recruiting event. This event is for representatives from companies looking to hire QA Bootcamp grads only.**

After accepting our placement agreement each employer will be able to access an online profile for each graduate from our program. The profiles include their photo, a brief bio, their LinkedIn and GitHub profiles.

If this is your first time participating in one of our placement events we will contact you with additional information. If you have questions please email Fuad Mak directly at fuad@sqasolution.com

Who are the students?

Each of the students at QA Boot camp was individually selected out of a pool of hundreds of applicants. Our students go through a rigorous application and screening process prior to acceptance into QA Boot camp, and were selected based on motivation, aptitude for learning how to test and interpersonal skills. Students come from a variety of backgrounds and experiences, including experience in corporate business, engineering, education, entrepreneurship, corporate business, law and other professional disciplines. There is also a small contingent of college students who have taken QA Bootcamp to enhance their career opportunities. QA Bootcamp students are a pool of top notch, dedicated, proven learners who have the requisite skills to make immediate contributions as junior-level developers.

Who are the staff?

The team at QA Bootcamp have extensive experience with software testing, test automation, teaching, and group facilitation. Many have tested software applications in both start up and corporate environments.

#SQASolutionShare on FacebookShare on Google+Share on LinkedInTweet about this on TwitterEmail this to someone

Were You Born to Test Software? Tell Your Story!

We are looking for proposal to speak at Software QA and Testers meet up.The testing community wants to hear your story of your experience and insight into software testing. Proposals are now being accepted through March 21, 2015. Each QA meet up event is approximately 60 minutes in length and interactive sessions are encouraged. Submitting a proposal is easy – just provide a short description on your talk and some brief information on your personal background in software testing.

We want to learn more about your success stories, innovations, and practical lessons that Software QA and Testers meet up attendees will be able to take back to the office and use in their professional work.

Popular Presentation Topics:

Test Management 
Test Techniques Mobile Testing
Test Automation Agile Testing Agile
Cloud Testing Security 
Performance Testing
Personal Excellence  Metrics Development
Leadership Mobile Applications Project Management

 
And if your topic doesn’t fit into one of these categories, we encourage you to submit it— we are always looking for new ideas. Great presentations help attendees learn more about specific technologies, how they work, how to implement them, what types of tools to have in their technology toolboxes, and more.
 

Submit a proposal

Your Name (required)

Your Email (required)

Phone Number (required)

Describe the topic you would like to discuss!

captcha

Enter the letters or numbers shown above:


Thanks for your interest!

#SQASolutionShare on FacebookShare on Google+Share on LinkedInTweet about this on TwitterEmail this to someone

Desktop Application Testing

by admin on January 23, 2015

Our Desktop QA experience includes multiple platform coverage and project-oriented approach.

Testing Types for Desktop Software

Most of the Desktop-oriented software we test goes through the following testing strategies:
testing

Localization Automated Exploratory Compatibility Ad-hoc Regression Cross-browser

Multiple Platforms We Support

We support a variety of platforms that include, but are not limited to: Windows-based platforms (workstations and servers), Linux-based platforms (and servers), OSX platforms (alongside the latest pre-release of Mountain Lion).

 windows  apple  unix
Windows  – our support extends to the following OS versions:

  • Windows 95/98/Me
  • Windows NT
  • Windows 2000 / XP
  • Windows Vista / Seven
  • Windows 8 / 8.1
  • Windows Server 2000
  • Windows Server 2003 / R2
  • Windows Server 2008 / R2
  • Windows Server 2012 / R2
 Mac – our support extends to the following OS versions:

  • MAC OS 9
  • MAC OS X 10.3-10.4
  • MAC OS X 10.5 – Leopard
  • MAC OS X 10.6 – Snow Leopard
  • MAC OS X 10.7 – Lion
  • MAC OS X 10.8 – Mountain Lion
  • MAC OS X 10.9.1 – Mavericks
 UNIX – our support extends, but is not limited to the following OS distros:

  • GNU/Linux:
  • Red hat , openSUSE,
  • Debian/Ubuntu
  • BSD derived:
  • FreeBSD 7-9,  OpenBSD, NetBSD, Darwin
  • Unix:
  • Oracle Solaris, IBM, AIX, HP-UX

Testing Across Verticals From A to Z

SQA Solution serves companies from a variety of industries from Retail to Media to Travel and more. Learn more about how we can help companies in your industry by selecting one below.

verticals

Travel Gaming Tech Telco Finance Entertainment Life Science

How We Do it

Your app needs to work where your users live, work and play – and that’s exactly where our testers are.

SQA Solution puts your app through rigorous testing using professional testers on real devices across locations and use cases that match your actual users.

Your custom testing team and QA Project Manager are the winning combination to reduce overhead and maximize app quality.

 

How it works

 form

Fill up a short form with basic information about your project as well as a brief description of your testing needs and specific instructions.

 QA Project Manager will get in touch with you over phone or email to clarify any remaining issues. You will also discuss the number of QA needed as well as mobile devices and their OS, deadlines, test plan and any other special requirements that you may have.

 call back
 agreement

Based on the supplied information we will prepare Teaming Agreement for you and will be ready to go.

Our professional QA Engineers and testers will start testing. You will receive all the reported issues submitted into bug-tracking-system so you may continue fixing the issues.

 desktop-testing-services

What it costs

Pricing starts as low as $25 per testing hour

 

Getting started with SQA Solution is more affordable than you may think. Find out how SQA Solution testing services fits into your budget with our form.

 

What our clients say

What your benefits are

 

  • Test your app on multitudes of real devices with professional testers.
  • Pay only for the time spent on testing. No hidden fees, required commitments or fine print.
  • Personalize your testing needs and hire SQA Solution On Demand.
  • Work directly with QA project manager that will assist you on every step of the process.
  • Get results faster and cheaper
  • Get testing results as soon as 24 hours after start.
  • Appreciate a professionally written bug reports and enhancements.

 

#SQASolutionShare on FacebookShare on Google+Share on LinkedInTweet about this on TwitterEmail this to someone

SQA Solution Testing Services

by admin on January 20, 2015

YOUR APP SUCCESS STARTS WITH TESTING

Testing is a vital component of App Success. Customers demand an app that performs well, moves quickly and is intuitive to use, stable and secure. The SQA Solution QA testers helps you every step of the way so you can manage the quality of your app from concept through launch and beyond.

Your Apps Are Everywhere — Your Testing Should Be Too

From mobile to web and beyond, SQA Solution has you covered.

 desktop  mobile  web

Testing Services for your Apps and Websites

Manage every aspect of your app’s quality, starting with:

 

testing

Localization Automated Exploratory Compatibility Ad-hoc Regression Cross-browser

Testing Across Verticals From A to Z

SQA Solution serves companies from a variety of industries from Retail to Media to Travel and more. Learn more about how we can help companies in your industry by selecting one below.

verticals

Travel Gaming Tech Telco Finance Entertainment Life Science

How We Do it

Your app needs to work where your users live, work and play – and that’s exactly where our testers are.

SQA Solution puts your app through rigorous testing using professional testers on real devices across locations and use cases that match your actual users.

Your custom testing team and QA Project Manager are the winning combination to reduce overhead and maximize app quality.

 

How it works

 form

Fill up a short form with basic information about your project as well as a brief description of your testing needs and specific instructions.

 QA Project Manager will get in touch with you over phone or email to clarify any remaining issues. You will also discuss the number of QA needed as well as mobile devices and their OS, deadlines, test plan and any other special requirements that you may have.

 call back
 agreement

Based on the supplied information we will prepare Teaming Agreement for you and will be ready to go.

Our professional QA Engineers and testers will start testing. You will receive all the reported issues submitted into bug-tracking-system so you may continue fixing the issues.

 desktop-testing-services

What it costs

Pricing starts as low as $25 per testing hour

 

Getting started with SQA Solution is more affordable than you may think. Find out how SQA Solution testing services fits into your budget with our form.

 

What our clients say

What your benefits are

 

  • Test your app on multitudes of real devices with professional testers.
  • Pay only for the time spent on testing. No hidden fees, required commitments or fine print.
  • Personalize your testing needs and hire SQA Solution On Demand.
  • Work directly with QA project manager that will assist you on every step of the process.
  • Get results faster and cheaper
  • Get testing results as soon as 24 hours after start.
  • Appreciate a professionally written bug reports and enhancements.

 

#SQASolutionShare on FacebookShare on Google+Share on LinkedInTweet about this on TwitterEmail this to someone

testimonials

by admin on November 19, 2014

 

#SQASolutionShare on FacebookShare on Google+Share on LinkedInTweet about this on TwitterEmail this to someone

{ 0 comments }

SOAPUI Interview Questions

by admin on November 17, 2014

interview-questions

SOAPUI Interview Questions

SOAPUI Interview Questions

#SQASolutionShare on FacebookShare on Google+Share on LinkedInTweet about this on TwitterEmail this to someone

If you believe what the analysts are saying, Opensource is only now becoming mainstream! A practitioner like you would say “What a blinding flash of the obvious!” and move on to your Jenkins.

There are problems with Opensource adoption. Functionality is not a problem by itself. By now, the abilities and weaknesses of all tools are known. What is often missed in the consequent problem – getting the various tools to talk to each other!

Given the provenance of these tools, you would think that all the tools would work cohesively together. But therein lies the rub – they don‟t! Well, ok, they do provide interfaces that allow you to get each of these tools to talk to each other, but they are like shy Englishmen – you have to spend the effort and time to get them to talk to each other. On their own, they do not integrate
and inter-operate.

Let us look at what needs to be accomplished in a typical Agile project:
* A set of requirements have to be built as a part of a sprint
* These are then translated to user stories
* These stories have to have the appropriate levels of priority, risk weightages
*  Test requirements, and test cases are then created and linked back to user stories
* Testing these cases will require, say, Selenium scripts to be created and executed. Again, these scripts have to be associated to builds.
* When these user stories are delivered, (as daily drops), they need to be tested „continuously‟
* The resulting defects have a life cycle of their own but do need to be traced back to the appropriate user story.
* Data across different tests are crunched to be able to throw up predictive „test efforts‟, test effectiveness and other predictive metrics

Now if you chose to manage this project using various Opensource, a typical selection would  look like this:

* Kunagi to manage sprints and user stories
* Test Link to manage test requirements, test cases
* Selenium to manage automation
* Jenkins for continuous integration and
* Bugzilla for defects.
* Jasper for test analytics

Each of these tools is great by itself (and has a great  following in the community). However, (there is always a „however‟ with Opensource tools!), they each come with their own way of setting up users, privileges, databases etc. What is lacking is seamless
integration – the ability to ensure that information and relationships are inherited both upstream and downstream.

The mainstream tools from HP or IBM do not have these issues as they are integrated (in fact working with other tools in the family is a key requirement) from the word “Go”. That integration, however, comes at a huge cost and does not go far enough. Which is probably why you are reading an article on Opensource tools, anyway!  There is a crying need for a single point solution to integrate all Opensource tools. Let us look at the characteristics that would define this integration tool:
Integration, not functionality
The existing toolsets are close to best-in-class. There is no need to add new functionality in the name of augmenting the tool. The relevant tool community knows what works best and it is ideal to leave those decisions to them. What is needed is a way to make them more coherent when they work with each other. This ensures a seamless integration across all the tools across the
entire lifecycle. If it can be done with minimal or no intervention, that is so much icing on the cake!

The key requirement is that the inter-component workflow be logically coherent.

Management & Control

Most Opensource tools are stand alone. What is required is the ability to form a clear, end-to end picture of the status of the project. Sufficient information for project management, estimation, risk analysis, functional and defect prioritization should be garnered. With both upstream and downstream integration, the tool should be able to provide complete lifecycle coverage, and work for different lifecycle models adopted. It should work with scalable development models, and across a multiplicity of projects within an organization. A defect tracking tool should be able to tag defects to requirements picked up from the appropriate
requirement tool.

Traceability
The ability to link together views across the different lifecycle elements is a functionality sorely missed in Opensource tools. In an ideal scenario, the tool should have the ability to identify a requirement and view its behavior downstream in terms of its behavior during test, its impact on release. Or, take a defect, and trace it backwards to weaknesses in requirement articulation,design or development. It should allow you to manage Agile user stories, link them to tests, link the tests to automated scripts, and link the test execution data to defects.
Analytics
Today the data generated at various points is only looked at that point with no attempt being made to glean insights from the patterns residing in the data. This, obviously, is because such analytics would mean integrating another tool with its attendant integration problems. Each of the Opensource toolsets stores a rich amount of data. Any integration tool should have, built-in, a powerful, customizable analytics engine that has the ability to weave the data together, and then leverage data along different dimensions. For example, analytics should be able to identify potential defect hotspots given a certain context. This feature will help testers to concentrate their efforts on the weakest interfaces instead of following a spray-and-pray approach. We need the ability to look beyond the data and to comprehensively predict patterns for the future.

Plug & Play Capability
Given the diversity of toolsets in the Opensource world, there is a need to achieve seamless integration across a diverse set of tools. One should be able to plug in different tools for various functionalities during the course of the project life cycle with minimal changes. The replacement could be another Opensource tool or even a COTS tool. Enabling the strong integration & interworking between Opensource toolsets is the need of the hour. These integrated features will help in the faster adoption of Opensource tools while being an invaluable productivity enhancer. It would pay for itself within a very short time merely from the effort saved, leave alone the management and control capabilities or analytics.

#SQASolutionShare on FacebookShare on Google+Share on LinkedInTweet about this on TwitterEmail this to someone

{ 0 comments }