Does anyone knows some good references to guide me in order to give automated tests, the best possible names? I know the rules but want good references to support some of the names that I used. Thanks in advance
Related
Hy people, I have a short question to ask:
is there any support for composite primary keys in Dapper.Contrib,
and if not, dose anyone have an implementation i can use?
Thank you !
Ok, so i did a bit of searching and came to the conclusion that DapperExtensions is more suited to my project needs as it supports composite primary keys via fluent mapping, while Contrib uses attributes. off course, it dose state here that Contrib dose not support composites, but I was still wondering if someone may have implemented it. In any case, DapperExtensions better fits my use case.
What type of coding knowledge is required for manual testing?
Is this required knowledge of java , perl or any other language?
I believe for manual testing there is no need for programming experience, but you have to know what can go wrong with the different input fields or when you interact with a screen or use a file as an input.
The most important is to do testing in a comprehensive way. You have to try everything in every possible way and check every value and behavior based on the specification.
And it's also important to have a knowledge what can be important for an everyday user.
I know testers who does manual testing and they are never tired of doing steps over and over again, if you get bored with it, you might forget to check something.
But if you are serious about testing, you have to learn testing frameworks to create tests. For example JUnit(for Java) or Selenium.
No need of coding knowledge required for manual testing. But it does not mean that anyone can conduct manual testing.For testing field you want skills to find different bugs ie.UI related bugs,functionality related bugs,performance related bugs,also you need good analytical skills and more important thing you need patience during testing. If you are very much interested to find something new every time then welcome to the world of testing.
Happy Testing.............
Please let me know what is the definition of Test Suit, Test Module, Test Block, Test Scenario and Test Cases, and what is the relation between them?
Thanks,
Somnath
The first thing you should know about asking for definitions is that words have multiple meanings depending on their context. If I give you an answer about what a Test Suite is (I assume you don't mean Suit as in a Suit and Tie) or a Module is and you take those definitions without thinking or applying them to your context, you won't make any sense. In fact you'll look stupid to anyone who knows better.
It's a better idea to try to understand how others are using the words and when. If you are in a team and they use a word you don't understand - ask. Lots of people use these words in different ways with different contexts and have different meanings. If you want to learn more, do some searches around for how people use those words in other contexts and see if there are any similarities or differences.
At the very least this should help you ask better questions.
There is TONS of information about testing on the internet. All the things you ask can be easily found if you google them. Have you even tried searching a bit?
I'm sorry but I would vote this question down but I can't because I don't have enough reputation.
So my question is simple and probably your answers will tell this is not possible...
Maybe on the first use of the dll file, I should see what is the MAC Address and put a restriction on that base? :)
Interesting question! You could manage a kind of white/black list (of course encrypted) in your DLL and handle the restriction code in DLL_PROCESS_ATTACH and then return TRUE or FALSE according to your needs.
You will need to search for specific technology or language and see what standard approaches do people use for this.
There is a trade off between how difficult it is to set up your product and the defence level. The tougher you make it for the bad guys, the tougher it will become to use your product.
You can use some sort of obfuscation and library encryption, which will work providing your user has a key (or password).
I am designing an internal API for a system I am writing. What are some best practises in API Design to think about?
The examples are in Java but the hints apply to any language.
How To Design A Good API And Why It Matters
Test Driven Development.
TDD will inform your design because it prompts you to ask questions like 'what do I need this to do' and it makes it easier for you to refactor with confidence, as you go thru your revisions. It also encourages making things as simple as possible, which is always a good thing.
Just remember that an API is a user interface. I try to focus on
doing one thing well,
maintaining a useful power-to-weight ratio,
avoiding cryptic names, and
explicitly specifying behavior via tests and effective documentation