Software QA/Testing Technical FAQs

Part:   1  2  3  4  5  6  7  8  9  10  11  12  13  14  15  16  17  18  19  20  21  22  23  24  25  26  27  28  29  30  31  32  33  34   35  36  37  38  39  40  41  42  43  44  45  46  47 

How can software QA processes be implemented without stifling productivity?
Implement QA processes slowly over time. Use consensus to reach agreement on processes and adjust and experiment as an organization grows and matures. Productivity will be improved instead of stifled. Problem prevention will lessen the need for problem detection. Panics and burnout will decrease and there will be improved focus and less wasted effort.
At the same time, attempts should be made to keep processes simple and efficient, minimize paperwork, promote computer-based processes and automated tracking and reporting, minimize time required in meetings and promote training as part of the QA process.
However, no one, especially talented technical types, like bureaucracy and in the short run things may slow down a bit. A typical scenario would be that more days of planning and development will be needed, but less time will be required for late-night bug fixing and calming of irate customers.

How to solve this issue - When developers blame testers for reporting bugs that is not reproducible on their machine?

Avoid this differences by taking screenshots and attaching them in bug tracking tool.
it seems that since the environment was not the cause then the "Steps to Reproduce" portion of the Bug report were lacking clarity. Screenshots along the way are a great way to prove a point, especially when you are dealing with something that is reproducible.
Sure as a test engineer we surely understand functionality and to an extent we understand the architecture of the software. Hence, we can surly say that some bugs are related to each other and some are not. So, We can introduc a column/field in our bug reporting format (What ever it is...a tool or an excel) for related bug ID.
This will actually be helpful for the development community too fix the bugs.
Actually Development environment should be same as Testing environment so that this issue will not arise. Make sure that before getting a Build the environment is same . Before Testing briefly go through with the Internal Release note. While Defect reporting mention proper Test data, steps etc. so that next time you can reproduce it.

Why do we recommended that we test during the design phase?
Because testing during the design phase can prevent defects later on. We recommend verifying three things...
1. Verify the design is good, efficient, compact, testable and maintainable.
2. Verify the design meets the requirements and is complete (specifies all relationships between modules, how to pass data, what happens in exceptional circumstances, starting state of each module and how to guarantee the state of each module).
3. Verify the design incorporates enough memory, I/O devices and quick enough runtime for the final product.

How to test a application in flash?

Manually testing flash animations is as simple as making sure that the objects do what they're supposed to do. manually mostly because flash isn't really a programming language. Most developers consider it to be a toy. So the big automation companies won't consider plug-ins for the flash objects.
If the flash application is a: E learning Application:
1. Need to know the the Hardware Configuration, becauase if this animation contains some heavy images or movie files then it works slowly, and which is a error.
so each and every images and movie should be of light weight, as far the quality says.
2. File naming convention
3. Flash detection
4. Objects should do what they are supposed to do
5. Etc.
If the flash application is a: Web Application:
1. File size, should be light weight, beacuase most of the user dont have high speed connection, load testing require
2. Quality of texts, images and movie

How test estimation (in terms of schedule, cost, resources required) will be done during developing of test plan?

Reads on the topic:
Factors that Influence Test Estimation

What kind of automated software used to test a Web-based application with a .NET (ASP.NET and C#...also SQL Server) framework?

Answer1:
Mercury makes some decent products. Quick Test Pro can be used for a lot of your requirements... It can be costly and mind-numbing at times though.

Answer2:
Selenium is a test tool for web applications. Selenium tests run directly in a browser, just as real users do. And they run in Internet Explorer, Mozilla and Firefox on Windows, Linux, and Macintosh. No other test tool covers such a wide array of platforms.
* Browser compatability testing. Test your application to see if it works correctly on different browsers and operating systems. The same script can run on any Selenium platform.
* System functional testing. Create regression tests to verify application functionality and user acceptance.

Answer3:
Ruby is becoming a preferred standard for testing
Perl is also used a great deal

Part:   1  2  3  4  5  6  7  8  9  10  11  12  13  14  15  16  17  18  19  20  21  22  23  24  25  26  27  28  29  30  31  32  33  34   35  36  37  38  39  40  41  42  43  44  45  46  47