Tag Info

New answers tagged

1

Preferable you want each test to run in isolation. You don't want any artifacts of a previous test laying around. So closing the browser after each test sounds as a good thing. A test follows three steps Setup: Launch browser, setup database, etc Test: Run single testcase Teardown: Cleanup I think you can use TestInitialize and TestCleanup methods, see ...


4

Great question. I see two issues, as follows. Using random data may lead to unrepeatable results. You can mitigate this by logging (or otherwise recording) every random choice you make, and then playing those choices back. That could be as easy as recording the initial seed to your random number generator, assuming your data does not change over time. ...


2

However you obtain test data, you would like to know that it is appropriate to the intention of the tests. When the test data is defined outside of the tests themselves, there is always the chance that the data will drift away from the intentions of the tests. The chance increases if the data is maintained by someone other than the test automators. If you ...


0

I think most people start by looking at the ISO standard.


0

As you already have a pretty nice list of area's where improvements can be found I think the next step is to find the most important thing to improve. I would focus on getting a continuous improvement process going. Possible roads are to introduce recurring retrospectives to identify parts of the process that need improvement.


0

Please identify the Different types of testing that you perform for the application Nature of bugs logged Types Regression Bug Trend How Early does tests find bugs How many priority bugs you find in early cycles What are the tools that QA uses to identify / report issues, Exceptions You need to identify your current state, pain points. Start Fixing ...


0

First of all you need to follow STLC if you want to test any software/Website properly with software testing standards.STLC is same for all. It does not matter what you are testing so STLC is base to start and complete testing with quality. Manual Testing - In most of application there are some areas which really need manual testing. So you need to find out ...


1

Unless you have a really good reason to repeat yourself, don't. Putting in an explicit login and logout step in each test is needless repetition if every test must perform a login and logout.


2

You can go either way. You might include these steps in each test, because they're actions that an actual user will take. Meaning that they can potentially fail in specific circumstances, and thus you'll want them linked to that specific test case. However, signIn() and signOut() look like actions every tester will perform manually as well for every ...


1

Coming back to share a solution that I find suitable. I wrote a framework based on nose2 (a python testing framework), that allows me to write hierarchical setups and teardown, thanks to such, a nose2 plugin. start_vms test_vms_are_started configure interfaces test_interfaces configure_dhcp test_dhcp configure_nat ...


0

When testing NFC components or devices, both analog (RF) and digital (protocol) tests must be performed. Analog tests measure such things as power levels, waveform quality, frequency accuracy, and modulation, while digital tests check for things like low-layer protocol exchanges, link timings and framing, as well as higher level protocols layers ...


0

In general, how many changes you tolerate in flight is tempered by your test coverage. Imagine a case where the team wants to complete a large refactor while implementing a new large feature. If you have robust test coverage, then this case may not be daunting. Presumably because the cause of errors can be identified with higher speed and certainty. ...


0

Unless you have a really really strong reason to refactor during testing and the unit/functional/acceptance test to check your changes, I'd say don't. Nathan Cooper points out that good code coverage will ease this pain of refactoring and I agree. Your question implies a distinct "code then test then deploy" workflow so changing stuff in the coding phase is ...



Top 50 recent answers are included