7

Ideally I would like to write the test based on a file that approximates what my script would be actually processing, rather a much much smaller sample size. If it were me, I would test functional correctness and scale independently. Fault isolation is easier that way. Your code/test/debug cycle can go more quickly too. The thinking here is that ...


3

Review business and functional specifications on early phases. This should not take much time. Don't be afraid of asking questions and to look silly. After all this is your job to find bugs and bugs might appear not only in the code but in specifications as well. Force your analysts to keep the specifications structured. Use mind mapping tools when you ...


3

I have found value from testing date time issues at all layers of an application. Which layer is determined by what I am trying to test. For instance: Testing Functional Logic: Assuming for a second that you don't have core logic built into your UI code (Model View Separation or something similar). It is often easier to test the core logic layer by ...


3

This is really less of an SQA question, and more about "how to I use web site analytics"? You can search for "website analytics" to learn more. And this might help: http://analytics.blogspot.com/


2

There are a few different solutions off the top of my head. There are several proxies that others have already mentioned that have APIs that can be made to listen on whatever port you need. They may not get granular enough though for what you need. If I were looking in this area I'd maybe take a look at Python's socket module.: http://docs.python.org/2/...


2

I know that it is doable, one of my previous employers integrated Wireshark (Ethereal then) analysis into its VoIP automation, using Perl AFAIK. I did some hacks by grepping on tcpdump and a filter, catching a packet or event I was looking for.


2

using your favorite script language would probably be the best solution, Peter suggested Perl and I'll add Python to the list, both have excellent modules to parse and analyze CSVs and XMLs and a lot of capabilities to help you in your tasks.


2

You see that as a problem, I see that as normal development process in an Agile team. There is a reason why The Agile Manifesto says Welcome changing requirements, even late in development Like you demonstrated very well in your question, it's very hard to know everything in advance. If you and your team really adopt Agile you will drop writing detailed ...


2

In a similar situation, I designed few critical end to end business scenarios and ran through both systems and compared the end results as well as crucial mid steps results in terms of output data. The selection of scenarios will be dictated by the level of data transformation as they go through the system. Also if the system supports search and reporting ...


1

This will depend on a number of factors, including: time/budget, data quality policy of your organization, data quality of the source dataset, complexity of each layer, etc. A general guideline is, as with any testing, to ask yourself "what could go wrong here?" at each step. For example, you could do data integrity at 1 and 2. But if you had a low budget ...


1

It will involve much more than data-migration testing. The first thing you should consider is perhaps how your customers (both internal and external) are affected. What do your customers need to do if this transition happens. If the application looks different, can the customers adjust to the new interfaces? The best way is to involve customers from day ...


1

As a QA Tester, you can take some time out before starting testing and using that for writing extensive use cases which will cover most of the scenarios. This will help you in later stages. However, no matter how much you strive to think all use cases, some are missed. We tester are humans too. Let the business analyst know about the specification they ...


1

Thoughts on error-prone modules detection One line of "defect prone modules" analysis may use the code complexity analysis to classify a module as "error-prone" or not. This would be based on the fact that a more complex code tend to have more potential bugs. There are several metrics in the code complexity analysis that we can use as ...


1

Have a graph with number of bugs on the left vertical y axis I would then have lines for factors that are relevant, e.g. lines of code, number of statements, line length, number of variables, global variables, etc. You could also have a formula that multiplies them together to give one line. I would stay away from trying to do multi-dimensional models ...


1

Instead of testing with csv / xml level. You can load the data into a database and run queries and obtain accurate results Create a Results DB with Run_Id (ex-ResultMMDDYYY_1) Load the source and destination data into the DB Run Queries for each source / destination tables and create a results table Fetch the data from results table and publish results You ...


1

There is a tool that was just launched by a company called XebiaLabs... I believe the tool is called TestView and does exactly what you are looking for. XL TestView is the first test results management and analysis tool that allows you to define and execute tests across your full spectrum of test tools, then aggregate and visualize the results to ...


1

You might want to take a look at Fiddler


Only top voted, non community-wiki answers of a minimum length are eligible