Articles
Windows FAQ
"Net.Pipe Listener Adapter - SMSvcHost.exe" Service on Windows 7...
Working w/google - How to add a inks toolbar? - Rank: 123 - Vote...
How to change handwriting input font? - love writing on my surfa...
Removing issch.exe - InstallShield Update Service Scheduler - Ho...
WIndows 8 Hangs on restart - I have Windows 8 Pro and when I res...
Who's Online
12 user(s) are online (4 user(s) are browsing Forum)

Members: 0
Guests: 12

more...
   All Posts (luck)


« 1 (2) 3 4 5 ... 32 »


PERL and C Programs for Validating and Checking -- Avignon Acceptance Testing System
Home away from home
Joined:
2007/11/1 12:10
Group:
Registered Users
Posts: 314
Level : 16; EXP : 56
HP : 0 / 389
MP : 104 / 8917
Offline
PERL and C Programs for Validating and Checking -- Avignon Acceptance Testing System

Avignon Acceptance Testing System - Open source acceptance test system that allows writing of executable tests in a language that the user can define. It uses XML to define the syntax of the language but, if the user chooses to extend the language, allows the semantics of the tests to be user-defined. Includes modules for testing web applications through either IE or FireFox, and modules for testing Swing and .NET WinForm applications also..

Posted on: 2/16 22:00
Transfer the post to other applications Transfer


PERL and C Programs for Validating and Checking -
Home away from home
Joined:
2007/11/1 12:10
Group:
Registered Users
Posts: 314
Level : 16; EXP : 56
HP : 0 / 389
MP : 104 / 8917
Offline
PERL and C Programs for Validating and Checking -

iMacros for Firefox - Free Firefox add-on to record and automate web interactions. Can use variables inside the macros, and import data from CSV files. Includes user agent switcher, PDF download and Flash, ad and image blocking functions. The recorded macros can be combined and controlled with Javascript, so complex tasks can be scripted. The EXTRACT command enables reading of data from a website and exporting it to CSV files. Full Unicode support and works with all languages including multi-byte languages such as Chinese. STOPWATCH command enables capturing of web page response times

Posted on: 2/2 21:24
Transfer the post to other applications Transfer


Microsoft Interview Question for Software Engineer in Tests about Algorithm
Home away from home
Joined:
2007/11/1 12:10
Group:
Registered Users
Posts: 314
Level : 16; EXP : 56
HP : 0 / 389
MP : 104 / 8917
Offline
Microsoft Interview Question for Software Engineer in Tests about Algorithm


Given a n array of positive and negative integers, find the subarray with max sum in O(n) and one loop.

Supose S is the array of integers, N the length and sum the current sum.
Let best be the solution at current step.We keep in x and y the limit of the best array
Initally,best = -INF and sum = 0.
Then

for(i = 0 ;i < N ; ++i)
{
if(sum <= 0) {sum = S[i] ; idx = i; }
else sum += S[i];
if(best < sum) {best = sum;x = idx ; y = i;}

The solution will be the subarray [x,y]. Complexity O(N) time O(1) memory and one loop.

Posted on: 1/12 17:43
Transfer the post to other applications Transfer


Software Testing -- What is a Test Case?
Home away from home
Joined:
2007/11/1 12:10
Group:
Registered Users
Posts: 314
Level : 16; EXP : 56
HP : 0 / 389
MP : 104 / 8917
Offline
Software Testing -- What is a Test Case?
A test case is a noted/documented set of steps/activities that are carried out or executed on the software in order to confirm its functionality/behavior to certain set of inputs.

Posted on: 12/29 17:06
Transfer the post to other applications Transfer


Five Principles of Bug Tracking
Home away from home
Joined:
2007/11/1 12:10
Group:
Registered Users
Posts: 314
Level : 16; EXP : 56
HP : 0 / 389
MP : 104 / 8917
Offline
Five Principles of Bug Tracking

1. Keep It One-on-One

Each ticket (aka "bug") is a link between two people: problem specifier and problem solver.


2. Close It!

Remember that a ticket is not a chat. You're not there to talk. You're there to close. When the ticket is assigned to you, focus on closing it as soon as possible.


3. Don't Close It!

Every time you raise a bug and create a new ticket, you consume project resources. Every bug report means money spent on the project: 1) money for your time spent finding the problem and reporting it; 2) for the time of the project manager who is working with the ticket and finding who will fix it; 3) for the time of the ticket solver, who is trying to understand your report and provide a solution; and also 4) for the time of everybody else who will participate in the discussion.


4. Avoid Noise — Address Your Comments

Every time you post a message to the ticket, address it to someone. Otherwise, if you post just because you want to express your opinion, your comments become communication noise.


5. Report When It Is Broken

Every bug has to be reproducible. Every time you report a bug, you should explain how exactly the product is broken. Yes, it is your job to prove that the software doesn't work as intended, or is not documented properly, or doesn't satisfy the requirements, etc.

Posted on: 12/8 21:06
Transfer the post to other applications Transfer


Software Testing -- What do I do if I Find a Bug/Error?
Home away from home
Joined:
2007/11/1 12:10
Group:
Registered Users
Posts: 314
Level : 16; EXP : 56
HP : 0 / 389
MP : 104 / 8917
Offline
Software Testing -- What do I do if I Find a Bug/Error?
In normal terms, if a bug or error is detected in a system, it needs to be communicated to the developer in order to get it fixed.

Posted on: 2014/11/14 21:33
Transfer the post to other applications Transfer


5 Tips to Write Better Tests
Home away from home
Joined:
2007/11/1 12:10
Group:
Registered Users
Posts: 314
Level : 16; EXP : 56
HP : 0 / 389
MP : 104 / 8917
Offline
5 Tips to Write Better Tests

* Treat Test Code as Production Code
* Use Test Patterns to achieve great readability
* Avoid Unreliable Tests
* Test at The Appropriate Level
* Use Test Doubles

Posted on: 2014/11/3 20:03
Transfer the post to other applications Transfer


Software Testing - Bug and Statuses Used During a Bug Life Cycle
Home away from home
Joined:
2007/11/1 12:10
Group:
Registered Users
Posts: 314
Level : 16; EXP : 56
HP : 0 / 389
MP : 104 / 8917
Offline
Software Testing - Bug and Statuses Used During a Bug Life Cycle


New
When a bug is found/revealed for the first time, the software tester communicates it to his/her team leader (Test Leader) in order to confirm if it is a valid bug. After getting confirmation from the Test Lead, the software tester logs the bug and the status of 'New' is assigned to the bug.

Assigned
After the bug is reported as 'New', it comes to the Development Team. The development team verifies if the bug is valid. If the bug is valid, the development leader assigns it to a developer to fix it and a status of 'Assigned' is given to it.

Open
Once the developer starts working on the bug, he/she changes the status of the bug to 'Open' to indicate that he/she is working on it to find a solution.

Fixed
Once the developer makes necessary changes in the code and verifies the code, he/she marks the bug as 'Fixed' and passes it over to the Development Lead in order to pass it to the Testing team.

Pending Retest
After the bug is fixed, it is passed back to the testing team to get retested and the status of 'Pending Retest' is assigned to it.

Retest
The testing team leader changes the status of the bug, which is previously marked with 'Pending Retest' to 'Retest' and assigns it to a tester for retesting.

Closed
After the bug is assigned a status of 'Retest', it is again tested. If the problem is solved, the tester closes it and marks it with 'Closed' status.

Reopen
If after retesting the software for the bug opened, if the system behaves in the same way or the same bug arises once again, then the tester reopens the bug and again sends it back to the developer marking its status as 'Reopen'.

Pending Reject
If the developers think that a particular behavior of the system, which the tester reports as a bug has to be same and the bug is invalid, in that case, the bug is rejected and marked as 'Pending Reject'.

Rejected
If the Testing Leader finds that the system is working according to the specifications or the bug is invalid as per the explanation from the development, he/she rejects the bug and marks its status as 'Rejected'.

Postponed
Sometimes, testing of a particular bug has to be postponed for an indefinite period. This situation may occur because of many reasons, such as unavailability of test data, unavailability of particular functionality, etc. That time, the bug is marked with 'Postponed' status.

Deferred
In some cases, a particular bug stands no importance and is needed to be/can be avoided, at that time, it is marked with a 'Deferred' status.

Posted on: 2014/10/17 15:50
Transfer the post to other applications Transfer


Software Testing -- How do I Find Out a Bug/Error?
Home away from home
Joined:
2007/11/1 12:10
Group:
Registered Users
Posts: 314
Level : 16; EXP : 56
HP : 0 / 389
MP : 104 / 8917
Offline
Software Testing -- How do I Find Out a Bug/Error?
Basically, test cases/scripts are run in order to find out any unexpected behavior of the software product under test. If any such unexpected behavior or exception occurs, it is called a bug.

Posted on: 2014/10/6 16:49
Transfer the post to other applications Transfer


Software Testing-- What is a Bug/Error?
Home away from home
Joined:
2007/11/1 12:10
Group:
Registered Users
Posts: 314
Level : 16; EXP : 56
HP : 0 / 389
MP : 104 / 8917
Offline
Software Testing-- What is a Bug/Error?
A bug or an error in the software product is any exception that can hinder the functionality of either the whole software or a part of it.

Posted on: 2014/9/22 20:37
Transfer the post to other applications Transfer



 Top
« 1 (2) 3 4 5 ... 32 »




Copyright (c) 2014 FYIcenter.com
Search
Main Menu
Login
Username:

Password:

Remember me



Lost Password?

Register now!