Tag Info

For the most part, I've gotten by with running simple SELECT queries with various WHERE filters. With my current position, though, I'm finding that adding more complex JOINs are necessary to really get what I need out of the database. I think you are answering your own question here. Basically - "it depends". Sometimes the position requires just a ...

Proficiency in SQL is just a start, there is something more that just being competent with the SQL syntax: Select, From, Join, Where, Order by, etc. A good Software tester in a job requiring DB skills needs to be willing to learn from the Developers and DBAs in the shop. The tester should want to refine and improve their DB data mining skill continuously. ...

If I am looking for a tester for either a database or for a heavily data driven application then the stronger they are with SQL the better. I think not only should they be comfortable with writing queries including JOINS, UNIONS etc, but they need to have a good understanding of what some of the different performance implications are around inserts and ...

If you work in a company using intensively with SQL databases, like in enterprise systems or online shops, you will very likely need at least basic skills in SQL, at least to create some test data in the database, to check results and so on. At least some DML knowledge, SELECT, INSERT, UPDATE, DELETE, will come handy sooner or later. But keep in mind it's ...

There are lots of ways to do this; some of the data points I have used in the past are: Build breakage: is the automated build compilation/test failure rate going up or down? Assuming an Agile development model, are the user stories complete and have they been reviewed by QA + stakeholders Has the code freeze been effective? Are developers still checking ...

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.: ...

[Disclaimer: This product is created by my company] We have a product call QuerySurge that allows you to fully compare data in the source tables with the data loaded into the data warehouse. Compared to other approaches, this seems to be the best automated method for validation.

I assume for the purposes of your question you are not concerned about testing anything upstream from the JMS queue. You may want to check whether the values in the XML are consistent with any constraints in the databases, e.g. uniqueness or maximum length. Depending on your circumstances, you may also want to test what happens when the values are not ...

I don't think that there can be such a concept as an "acceptable" defect arrival rate, in the sense of a target number as you typically want to discover them as fast as possible. So, in english, you want to find as many bugs as you can. The key way to read that metric is that you want a consistent arrival rate over time, i.e. you want the defect arrival ...