Example of a Stress Testing

Stress Testing is a part of software testing life cycle. Software tester also concern on how they can create, find and test a test case and scenario on executing a stress testing from the references of a product requirements.

Here is a scenario and case:

Scenario: After a user was click a button to submit a data and it was successfully all required text box are correct and accepted in the server, the scenario is, what if the connection is lost from client to the server.

Case: Test if all data that being submitted is being cache or not, or the session is expired or not.

Procedure: Assuming that all required value in the text box is now complete then clicking a button to submit, after submit button is click, unplug the LAN connection in the pc client that connected to the server.

Expected Results: Will, it is only an example of stress testing and it depends on the product requirement if data should be cache or not, or the session expired and should repeat it again all data that inputted or the session will not expired and the session is still alive after re-plug the LAN connection and refresh it again.

Point: The point here is how to execute using a stress testing. The point is the simple idea in a stress testing strategy.

Different of built-in tools and programming in SQA engineering

Nowadays, software development is to become heavily up in our generation for development of a application that is why software quality assurance engineering is also required to have a knowledge in programming like JAVA or RUBY language but also it depends in the company. Some software development hired a QA engineering knows how to create a script and other are knows on the deeply manual testing.

Example of the built-in tools that they use by the tester is like a Selenium IDE, QTP, JMeter that they use for functionality testing of the application system. Now, the different is you cannot customize your code for the expected results based on the expected output from the system requirements of the application. Built-in tools is you can only use on what the built-in function are available about the tools. But what if you want to add your own cuztomization about your style on testing manipulation. Creating a script like the use of JAVA or Ruby, that they have some libraries that you can use like a selenium library jar files that was extended to the Java core and Ruby core and also you can use the if statement, while statement of a logical style in programming for every test cases or scenarios, you can upgrade, plugin the different libraries and extension and run it in the black window of the command line. 

Software Quality Assurance Automation Testing

In the world of software development, application development, game development, software tester is proven that they have a big picture for the successful delivery of the application. Software tester, is a part of a software quality assurance department that they tend to follow the test cases, test scenarios that was created by the senior quality assurance staff. Mainly there are two types of a tester that they perform a testing execution, first is manual tester, for the manual testing execution from the first up to the last of steps per test cases and second is the automation tester for automation testing who create a script and execute a testing using a scripts.

Manual and automation tester are both the same main job description, to test and finding bug and error. The only different between manual and automation tester, is manual tester is focus only on a testing without using a tools that they use for QA engineering like Selenium, QTP. Automation tester has a byte of knowledge in programming and also they knows on how to use the built-in tools for QA engineering. They use a JAVA and or Ruby language for the development of scripts. 

What is the benefits of Automation Testing?

It was exactly for regression testing to re-test the bug fixing already by the member of the software developer from the previous cycle that was already detected by the QA tester. Regression is the concern of the manual tester because you will go back from the top to down of test cases lists to re-test per test cases and check if the bug is fixed already. So much time to consume for regression if you have manually test the system from the beginning steps up to the last. While Automation tester is they focus on scripting development and only less than 5 steps of command to execute a script and then they will show you a results from a regression testing.

Selenium RC intermittent in the command line

java.lang.NullPointerException
at junitss.DatadrivenJUnit.testDatadrivenJUnit(DatadrivenJUnit.java:109)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at junit.framework.TestCase.runTest(TestCase.java:168)
at junit.framework.TestCase.runBare(TestCase.java:134)
at com.thoughtworks.selenium.SeleneseTestCase.runBare(SeleneseTestCase.java:249)
at junit.framework.TestResult$1.protect(TestResult.java:110)
at junit.framework.TestResult.runProtected(TestResult.java:128)
at junit.framework.TestResult.run(TestResult.java:113)
at junit.framework.TestCase.run(TestCase.java:124)
at junit.framework.TestSuite.runTest(TestSuite.java:243)
at junit.framework.TestSuite.run(TestSuite.java:238)
at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:83)
at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50)
at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197)


This message having encountered when your automation script using java was not successfully run.

1. Restart the selenium RC
2. Make sure the libraries and or jar files is completed in your editor.