New answers tagged

0

Cross browser testing can be done with BrowserStack & CrossbrowserTesting. Both allow a 30 day trial. They have numerous emulators for physical devices. Chrome allows Toggle Device mode (Ctrl+Shift+M) Edge has Emulation Mode which can be navigated via inspect element. I believe BrowserStack covers most of the devices and their versions, so we can ...


1

As of my reading- Red-Box Testing: It is nothing but a Protocol testing. User / Client can apply any techniques to accept the project. They will apply white box or grey box or black box for accepting the project. So we are calling the user acceptance testing as a red box testing. Yellow box Testing: Yellow box testing is checking against the warning ...


1

Yellow Box Testing includes the Acceptance Testing Techniques while Green Box Testing contains the Release Testing Techniques.


1

You can check this question and answers, you can find some explanations in there: http://stackoverflow.com/questions/3620990/what-is-red-box-yellow-box-and-green-box-testing


0

The bug is high severity only so we send the application to the client and find out the severity is priority or not. If its priority then we ask him to wait. Here we found defects/bugs in the last minute of the delivery or release date- Then we have two options Explain the situation to client and ask some more time to fix the bug. If the client is not ...


2

Testing usually falls to a tester/ test engineer, the designing and maintenance of test cases, writing necessary testing code and all the meta-work usually falls to a team lead such as an SQA engineer. To help build a software quality assurance and testing toolbox, here is a list of tips, tools, tutorials, blogs, services, and miscellaneous other resources ...


1

There is no magical answer for this. Your options include: Hide the bug and hope that the customer does not find it before you can deliver a fix. Delay the delivery until the bug is fixed. Talk to the customer about the bug and let them decide how they want to proceed. The choice depends on your circumstances, and no one here knows those as well as you ...


3

Deciding to release with severe bug (and escalate next release with a fix) or postpone release is business decision. QA cannot "assure" quality. QA can "assist" business side with information about quality and process. Business decides what is best allocation of resources: more development, or more testing, or more management and control. In situation like ...


1

I'm using PrtScr It is quick, and simple... Lets you take a full screen screenshot, or draw the area you want... It also lets you draw with a red line "pen" And you can save the image where you want, or save it on desktop, or simply copy the image to clipboard... Try it...


4

This is a simple, if uncomfortable, situation to be in. Unfortunately, it does happen from time to time and you need to be ready for it. The fact that the defect has been found close to the deadline is, in the short term, irrelevant. Your team has found a high severity defect, so you report it. Given the short timescales, you ensure that everyone who ...


1

I have here 2 free testing tools: Nimbus and HotShots. I see the Nimbus (https://nimbus.everhelper.me/screenshot.php) as a rising star of screenshot tools for testers. It enables some after-capture functionalities such as highlighting, frames, text comments etc. Nimbus: It is available as Chrome and Firefox addons, works on Android and runs on Windows. ...


2

There are number of tools available in the market for Screen capture- Greenshot: PicPick: http://ngwin.com/picpick/update?AVGAFFILIATE=11859 Gadwin PrintScreen: http://www.gadwin.com/download/ Jing : https://www.techsmith.com/jing.html SnagIt: https://www.techsmith.com/snagit.html


-1

Try Awesome screenshot. It has plugin for both chrome and firefox Click here for Awesome Screenshot


0

For an ERP system, scenarios differ from other test phases in their length and depth. For example, a functional unit test of a sales order might go into depth to check every facet of a single order - the sales partner (sold to / ship to / bill to), the material and material type, shipping point, pricing conditions, incoterms, freight charges, etc. ...


0

After checking out TestLodge, I think it's fine if you keep a single Test Plan for your software and create a separate Test Run for each new version of your software, with the version included in the Test Run's name. The "best practices" for associating a test run with a software version would be to ensure that it is easy to determine in the future exactly ...


0

I would suggest you work with the developers to find out what are the core functions that all releases have in common, that becomes your initial Test Plan and also a potential source for your regression testing for the overall product. While having a discussion with the developers ask them which are the areas with the most risk both for the core ...


4

Yes and you're definitely ahead of the crowd already with the plan you've laid out. Additional considerations: In addition to using a Page Object Model, consider a central place for hard coded values (simple methods that return a string in some cases). So the identifiers for the css locator for last_name are in one place (along with other css element ...


0

If your company has a subscription to PluralSight I would recommend them for some of your initial training. Microsoft offers several certification programs here are a few: https://www.microsoft.com/en-us/learning/mcsd-application-lifecycle-management.aspx



Top 50 recent answers are included