What is Robot Army Testing? Where is it used? How can I learn it?
I'm not sure that it exists. There's Rational Robot, an automated testing record-and-playback tool, but you have to buy it. I've yet to hear of Robot Army testing, however, although I agree with Nick - it sounds AWESOME :)
The only mention I can find of it ANYWHERE is on:
http://www.mail-archive.com/wtr-general#rubyforge.org/msg07756.html
So maybe it's also known as MBT (Model Based Testing)?
If so, take a look at http://en.wikipedia.org/wiki/Model-based_testing for information on that and some handy links to tutorials etc.
Hope that helps!
If by "Robot Army Testing" you mean assembling a suite of automated tests on a grand scale (sort of xUnit on steroids) then this presentation provides a helpful introduction. It is also known as Model-Based Testing.
edit
As uberRouse notes, the use of randomly generated values in testing is interesting. I first came across this in 2005. It was a tool called Agitator from Agitar Software which took manually written unit tests and expanded on the coverage by plugging in random values and edge cases.
This term is not on WikiPedia. Everything, that is at least a little popular technology appears there quickly. Are you sure you don't misspell it?
Robot Framework maybe? We use it and it's great!
BTW, it sounds like web-site DDOS testing ;)
Related
One of the problems our group is having is in regards to sharing relevant information between the Devs, Devs in Test and QAs.
How is this typically done in the industry?
For instance, our devs typically follow TDD with CI/CD pipelines offering the capability to illustrate code coverage. Do devs in test and QAs typically review coverage numbers prior to construction of integration and manual test plans?
How are devs typically communicating edge cases and relevant test procedures to the testers these days?
Finally are there any great resources (docs, podcasts etc) that discuss these types of things?
In my experience, there isn't a whole lot of such information shared between DEV and QA, apart from the requirements, things like API documentation and maybe usage examples. The reason is simple: Developer tests (unit, integration) are usually whilebox tests, while tests performed by QA are usually blackbox tests (i.e. oblivious of the code being tested). What use is a coverage report for blackbox tests?
What i think in this case is , If we use tools like JIRA, then in each story/ticket on which Dev is working he/she should mention all the related doc, details and major technical specifications like which module/API/project_layer he has worked on to solve this particular requirement with atleast few of his unit test links to this ticket will certainly help while testing.
And this thing also helps in accounting of code changes done in the project for the tickets so that we can also guess the major regression areas.
Let me know if u find this helpful.
Thanks
is there sample/open_source application for download that is covered with tests(integration, unit, ...) and could be example how testing should be done? We want to learn our junior programmers how tests should be written(ok ok, and we(seniors) want to learn, too :))
Thanx
I would bet the JUnit framework is well covered with unit tests :-)
You can download the sources from here .
Have a look at public metrics of sonar. It scans a lot of open-source projects. Just pick the ones with the highest coverage ;)
Coverage list open-source projects
As part of a new job, I have to devise and implement a complete test strategy for the company's new product. So far, all I really know about it is that it is written in C++, uses an SQL database and has a web API which is used by a browser client written using GWT.
As far as I know, there isn't much of an existing strategy, except for using Python scripts to test the web API.
I need to develop and implement a suitable strategy for unit, system, regression and release testing, preferably a fully automated one.
I'm looking for good references for:
Devising the complete test strategy.
Testing the web API.
Testing the GWT based application.
Unit testing C++ code.
In addition, any suitable tools would be appreciated.
Testing Computer Software is a great soup-to-nuts book on the entire testing process. In addition to the items you mentioned, you'll need to think about other types of testing (performance, security, localization, stress testing, to name a few) and how to manage the test process; test plans, issue tracking, test data, test cases, in addition to the tools.
There's a lot there, and you can't do everything at once. I think a phased approach would be best, where you identify the gaps, weaknesses, and risks in the current process, prioritize them, then set up a high level plan to address them one by one.
Software QA Testing and Test Tool Resources is a good starting place for finding some tools to fit your process. StickyMinds is a nice web site dedicated to software testing, and the folks here at StackOverflow certainly know their stuff, so don't be afraid to ask.
Good luck :)
You can find a ton of excellent information on testing and developing a test strategy in general over on James Bach's blog. Specifically by searching through it for tips on testing strategies.
James is an excellent resource for information about how to do great software testing.
Best of luck.
There's a good conversation here on The Purpose of a Test Strategy.
As testing tools you could use Selenium for web testing and CppUnit for c++ unit testing.
I'm looking for good reference material regarding the use of ABAP Unit Test Classes.
I'm interested in any of the following:
Documentation on the functionality
Best Practises
"How To Guides"
Blogs/Books on people's experience in using test-driven development in a SAP environment, particularly what sort of scenarios leans themselves to test-driven development & how you get around the dependency of SAP on business data.
There is some documentation in sap.com.
Also, there is a German PDF (see here) that may be helpful if you know some German ;-) At least it contains a few email addresses of people that may be able to help. Not sure because the PDF is from a conference in 2003, so the contact info may not be too up to date.
Lastly. there seems to be a German book (on Amazon Germany) .. again not sure if that helps you.
Wondering if you'd checked these links...
https://wiki.sdn.sap.com/wiki/display/ABAP/ABAP+Unit
https://wiki.sdn.sap.com/wiki/display/ABAP/ABAP+Test+and+Analysis+Tools
Thanks.
I recently wrote a blog article on my experiences here: Adopting Test Driven Development using ABAP Unit
There is some documentation in SE24 for class CL_AUNIT_ASSERT. Doing a where-used on the class gives an indication of how it is meant to be used.
There also is a 5 part blog series on SAP SDN
UPDATE: There is now also an excellent course on ABAP Unit on OpenSAP.com. It is called
Writing Testable Code for ABAP
The URL for the course is: https://open.sap.com/courses/wtc1
So I'm interested in hearing different thoughts about what is the best way to go about unit testing XNA Game/Applications. Astute googlers can probably figure out why I'm asking, but I didn't want to bias the topic :-)
I would that this question is geared more toward the approach of unit testing in game development. I mean, XNA is a framework. Plug in NUnit, and begin writing test cases while you develop.
Here is a post on SO about unit testing a game. It'll give you a little insight into how you need to think while progressing.
XNA BOOK
This book shows how to code in XNA but the entire book is based on NUNIT testing. So while you are coding the projects in the book, he also shows you how to write the scripts for NUNIT to test the XNA code.
VS2008 has a nicely integrated unit testing framework. (I assume you're using using the XNA 3.0 CTP with your Zune.)
The Microsoft testing framework is now available in Visual Studio 2008 Professional and up. If you have this software you already have all the software that you need to start testing your games.
Here are two links that will get you started:
Unit tests Overview - http://msdn.microsoft.com/en-us/library/ms182516.aspx
Creating Unit Tests - http://msdn.microsoft.com/en-us/library/ms182523.aspx
If you only have the Visual Studio 2008 Express than you need to use some other testing framework. NUnit is probably the best one, some people even prefer it to MSTest.
After you have all the software you need you can start adding tests for your code.
Here I've posted some basic techniques about unit testing games that you might find useful.
Have you done unit testing before?
If you haven't I could posbily give you some more hints and resources
You should give Scurvy Test a try. Have not used it my self but it looks promising.
I know this is an old post, but for other people wondering how to best go about testing their XNA Games, there is another option. The built-in testing in Visual Studio is definitely great, but is not well suited for games. Everytime a value is needed, you have to pause the game, and then either hover over the variable, go to quick watch, or add a watch. Then you can see the value of the variable at that frame. To see the value again during another frame, you must pause your game, again. This can be a big hassle. Therefore I have created a debugging terminal to run on top of your game. It allows you to see values of variables, invoke methods, and even watch a variable change in real-time all while you game is running! To find out more, visit: http://www.protohacks.net/xna_debug_terminal/
The project is completely free and open source. If you like it, feel free to tell others using XNA Game Studio about it. Hopes this helps out!