I want to be able to create the test's inside the Web-UI instead of writing them in code. Also i want to automate the tests and have extensive reporting.
I am restricted to htmlunit because the websites i am testing are testable with htmlunit.
You can define the test steps in other ways, see WebDriver recorder, WebTest and Wetator.
There is Spring MVC Test HtmlUnit also.
Related
We have been using the Jmeter for the API's functional and performance test activities.
Is there a possibility to generate the documentation (similar java docs, API docs) for the JMX projects that we have been developing?
Each JMeter's Test Element has "Comments" section which can be used for explanation of what this element is for:
It's possible to create a JMeter Test Plan using Java language and JMeter API, see JMeter Command Line Overview: 5 Ways To Launch a Test for more details. There is also jmeter-from-code sample project you can use as a reference, normal JavaDoc will be available out of the box
There is JMeter DSL project which provides easy and handy way of creating a JMeter test plan, however it doesn't fully support all the features. For basic test plans it should be faster and easier than point 2
There is Taurus tool which provides possibility to create JMeter scripts in a declarative manner using YAML and YAML naturally supports comments
I am new to Native Script with Angular. I need help for writing Unit Tests for Angular components by mocking a service with Karma and Jasmine.
I have followed the Native Script Unit Testing docs (https://docs.nativescript.org/tooling/testing) to integrate the Unit Test environment but not much details available how to write test.
Please suggest me how to write or give some repo links of NS + ng Unit Testing.
Thanks.
The examples from nativescript-angular repo might help you write your unit test cases.
I've implemented a testing unit using spring (mock mvc), and I'm looking for a tool to run this unit in many threads/processes (so it will act as load testing for my server). I've seen applications like the grinder and jmeter but I don't want to re-write the entire unit, but just to use the existing one. Any ideas?
JMeter is able to execute existing JUnit tests via JUnit Request sampler, all you need to do is to drop jar(s) with your test along with dependencies somewhere in JMeter classpath and restart JMeter. Once done you'll be able to see your classes and methods in JUnit Request sampler dropdown and execute them in multithreaded manner.
See How to Use JUnit With JMeter guide for more detailed instructions and explanations.
Currently I have a small suite of integration tests running against my web-server which makes a request and asserts some assumptions on what the responses should be. These are written in Ruby generating http requests.
I've been looking at Gatling as a stress testing tool but I'm wondering if it could also be used for an integration tests as well. This way all the endpoint requests could be reused across the the stress tests and the integration tests.
I'm probably losing something here from not having the BDD of RSpec but gaining not having to create the same tests twice.
Does anyone have any experience of using gatling in this way?
You can use the Assertion API and set up acceptance criteria.
However, Gatling isn't a browser and won't run/test your Javascript, so this approach is only realistic when dealing with server side content, such as testing REST APIs. Here's an example.
I am currently testing MVC 3 Controller and views using HTML and notepad. Is there other ways to do testing if you cannot modify the code? Like for example creating a seperate project to do testing?
Assuming that you have the capacity to create a test project or two which can tap into the web application, you essentially have to basic tools at your disposal:
Unit tests
Coded UI tests
Unit tests are used to test specific components of your application. If your application has a nice architecture which takes dependency injection into account, there is very little in MVC that you cannot unit test to some extent. The advantage of unit tests is that they help find the source of bugs in your code (as they are small, targeted tests) and that they help prevent regressions when refactoring or adding new functionality.
Coded UI tests are used to test user-facing features in your application and serve as integration tests which allow you to test the entire application stack, including the user interface. They are recorded just like you would record a macro in MS Office.
Both of these can be done nonintrusively. You'll need access to the original solution (or at least the DLLs and a hosted version of the website at the very least.
For more information on unit tests: http://msdn.microsoft.com/en-us/library/dd264975.aspx
For more information on Coded UI tests: http://msdn.microsoft.com/en-us/library/dd286726.aspx